PC/Transfer 1.8 Installatoin and Operations Guide

PC/TRANSFER™ Automated File Transfer

Installation andOperations Guide

Version 1 Release 8

PC/TRANSFER is a PC–host file transfer system that allows data to be transferred between any PC that is running TCP/IP, a 3270 emulator, or an APPC interface, and a host computer running TCP/IP FOR VSE™ and CICS.

Copyright © 2000 by CSI International

All Rights Reserved

RESTRICTED RIGHTS LEGEND

Use, duplication, or disclosure by the Government is subject to the restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013.

This material contains confidential and proprietary material of Connectivity Systems, Inc. (hereafter referred to as CSI International and CSI) and may not be used in any way without written authorization from CSI International. This material may not be reproduced, in whole or in part, in any way, without prior written permission from CSI International.

Permission is hereby granted to copy and distribute this document as follows:

• Each copy must be a complete and accurate copy.• All copyright notices must be retained.• No modifications may be made.• Use of each copy is restricted to the evaluation and/or promotion of

CSI International’s PC/TRANSFER product or in accordance with a license agreement.

PC/TRANSFER Version 1 Release 8Installation and Operations Guide

April 2000

Published by CSI International8120 State Route 138Williamsport OH 43164

Phone: 800-795-4914

Fax: 740-986-6022

Internet: http://www.csi-international.com

E-mail: [email protected]

Technical Support: [email protected]

Documentation comments: [email protected]

http://www.csi-international.com

mailto:[email protected]



This documentation applies to Release1.8 of the program product PC/TRANSFER.

Original Printing........................11/01/1999Last Revised ...............................04/07/2000

PC/TRANSFER is a proprietary product of CSI International. It cannot bereproduced, changed, copied, or stored in any form (including, but not limited to, copies onmagnetic media) without the express prior written permission of CSI International.

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 NT2) Microsoft Windows 3.13) OS/24) MS-DOS or PC-DOS

You are hereby granted the right to install the Microsoft Windows and/or the OS/2 versions ofthe PC component of PC/TRANSFER on as many PCs as you require, as long as all of thePCs you install it on connect to and use the same mainframe component of PC/TRANSFER.

The DOS version of the PC component of PC/TRANSFER uses a DOS-Extender developedby Phar Lap Software Inc. The run-time license agreement between CSI and Phar Lap SoftwareInc. requires that each distribution diskette from CSI be installed on a single PC. If the PC is aserver 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 runPC/TRANSFER, additional distribution diskettes are available from CSI for a small fee.

TABLE OF CONTENTS

I

GETTING STARTED........................................................................................................................1Introduction .............................................................................................................................. 3Features of PC/TRANSFER ...................................................................................................... 4PC/TRANSFER Overview .......................................................................................................... 6

Download Procedure....................................................................................................... 8Upload Procedure ............................................................................................................ 9

New for This Release................................................................................................................ 10Migration Requirements ......................................................................................................... 13System Requirements .............................................................................................................. 16Installation for a VSE Host ....................................................................................................... 19

VSE Installation Step 1 - Load Distribution Tape .......................................................... 20VSE Installation Step 2 - Release Install Job ................................................................. 20VSE Installation Step 3 - Supply LIBDEF .......................................................................... 20VSE Installation Step 4 - Define the Host Control File................................................. 21VSE Installation Step 5 - Define Host Activity Log File ................................................. 22VSE Installation Step 6 - CICS/VS Table Additions....................................................... 23VSE Installation Step 7 - BIM-TMAN Setup ..................................................................... 25VSE Installation Step 8 - Customization ......................................................................... 26VSE Installation Step 9 - Activating the TCP/IP Interface .......................................... 26VSE Installation Step 10 - PC Program Installation ...................................................... 27

Installation for a MVS Host...................................................................................................... 29MVS Installation Step 1 - Load Distribution Tape......................................................... 30MVS Installation Step 2 - Install SVC............................................................................... 30MVS Installation Step 3 - Customize JES Interface...................................................... 31MVS Installation Step 4 - Define the Host Control File ................................................ 32MVS Installation Step 5 - Define Host Activity Log File................................................ 33MVS Installation Step 6 - CICS/VS Table Additions ..................................................... 34MVS Installation Step 7 - BIM-TMAN Setup.................................................................... 37MVS Installation Step 8 - Customization........................................................................ 38MVS Installation Step 9 - PC Program Installation....................................................... 39

Connecting the PC to the Host............................................................................................. 41PC/TRANSFER Connection Settings................................................................................ 42

Single Connection Definition ................................................................................... 42Connection Profile Definitions.................................................................................. 43Profile List Dialog......................................................................................................... 44Profile Details Dialog.................................................................................................. 45Using Connection Profiles In Manual Transfers ..................................................... 46Using Connection Profiles In Automatic Transfers ................................................ 46LU2 Settings.................................................................................................................. 47TCP/IP Settings ............................................................................................................ 49APPC Settings.............................................................................................................. 50

LU2/3270 Connections Using Microsoft Windows. ...................................................... 52HLLAPI Application Interface ................................................................................... 52PATH Statement.......................................................................................................... 52DLL Specification........................................................................................................ 52Verify Session ID .......................................................................................................... 53PC/TRANSFER Configurator....................................................................................... 53

LU2/3270 Connections Using OS/2................................................................................. 54HLLAPI Application Interface ................................................................................... 54Verify Session ID .......................................................................................................... 54

LU2/3270 Connections Using DOS.................................................................................. 55BIMDOSCK Program................................................................................................... 55

TABLE OF CONTENTS

II

IRMA(DCA) E78+ Special Processing.......................................................................56TLINK Special Processing............................................................................................56

TCP/IP Connections to the Host......................................................................................57Overview ......................................................................................................................57Activating the ‘Listen’ Task .......................................................................................57

APPC Connections Using Microsoft Windows or OS/2................................................58APPC Connection Overview ....................................................................................58VTAM Definitions on the Host for APPC...................................................................59CICS Definitions on the Host for APPC ....................................................................60PC/TRANSFER Definitions for APPC...........................................................................61PATH Statement for Windows version .....................................................................61APPC Interface Configuration on the PC ..............................................................61IRMA Workstation for Windows (APPC)...................................................................62RUMBA (APPC).............................................................................................................63DynaComm/Elite (APPC)...........................................................................................64Communications Manager/2 for OS/2 (APPC).....................................................65IBM Personal Communications PC/3270 (APPC) ..................................................66Attachmate Personal Client (APPC) .......................................................................67

Logon/Logoff Scripts ................................................................................................................69#LOOK .................................................................................................................................69#AT........................................................................................................................................70#SEND ..................................................................................................................................70#BYE .....................................................................................................................................71Example Logon Script .......................................................................................................72Example Logoff Script .......................................................................................................73Example Automatic Transfer Scripts...............................................................................73BIMLOGON - Logon/Logoff Script Recorder ................................................................74

Option Pull Down ........................................................................................................74File Pull Down ...............................................................................................................75Recording A Script ......................................................................................................75

Security Overview.....................................................................................................................77Security for Host Maintenance........................................................................................77Security for Transfers ..........................................................................................................77

Default Security Mode...............................................................................................77Require User Definition Mode...................................................................................78User Security Groups...................................................................................................78Dataset Access Security............................................................................................79VSAM Security..............................................................................................................79Access Security Definitions........................................................................................79

USING PC/TRANSFER...................................................................................................................81Using The PC Transfer Program - BIMFTR(x) ..........................................................................83

Starting the PC Program from within Microsoft Windows 95/98 or NT 4.x ...............83Starting the PC Program from within Microsoft Windows 3.1 or NT 3.5.x .................83Starting the PC Program from within OS/2....................................................................84Starting the PC Program from the DOS Command Line............................................84Signing On...........................................................................................................................86PC File Transfer Window....................................................................................................87File Pulldown .......................................................................................................................88Transfer Pulldown ...............................................................................................................90Help Pulldown.....................................................................................................................91Dialog Boxes .......................................................................................................................92General Settings Dialog....................................................................................................92

TABLE OF CONTENTS

III

Interface Settings Dialog ................................................................................................. 94Log Settings Dialog ........................................................................................................... 95File Dialog ........................................................................................................................... 96Download Selection Dialog............................................................................................ 97Generic LIBQUE Values for Downloads......................................................................... 98Download Destination Dialog ........................................................................................ 99Upload Selection Dialog.................................................................................................. 101Generic LIBQUE Values for Uploads .............................................................................. 102ASCII Translation Option .................................................................................................. 104CRLF Transfer Option ........................................................................................................ 105Transfer Status Dialog ....................................................................................................... 106

Using The PC Automatic Transfer Program - BIMAFT(x)..................................................... 107Starting BIMAFT(x) from within Microsoft Windows 95/98 or NT 4.x........................... 108Starting BIMAFT(x) from within Microsoft Windows 3.1 or NT 3.5.x ............................ 108Starting BIMAFTO from within OS/2 ................................................................................ 109Starting BIMAFTD from the DOS Command Line......................................................... 109BIMAFT(x) Main Program Window.................................................................................. 111File Pull Down ..................................................................................................................... 112Process Pulldown............................................................................................................... 113Help Pulldown.................................................................................................................... 114Auto Settings Dialog ......................................................................................................... 115Script Recording................................................................................................................ 117

Signon Dialog.............................................................................................................. 121Execute PC Program Dialog .................................................................................... 122Automatic Transfer Options Dialog......................................................................... 123Host Transfer Send to Netname Dialog.................................................................. 124

Automatic Transfer Script ................................................................................................ 125#KEEP............................................................................................................................ 127#SENDTO ...................................................................................................................... 128#SIGNON...................................................................................................................... 129#OPTION ...................................................................................................................... 130#IFEXISTS ....................................................................................................................... 133#IFNOTEXISTS ............................................................................................................... 133#ENDIF .......................................................................................................................... 133#DOWNLOAD ............................................................................................................. 135#UPLOAD ..................................................................................................................... 137#TRANSFER ................................................................................................................... 139#EXEC........................................................................................................................... 141#COPY.......................................................................................................................... 142#RENAME ..................................................................................................................... 142#MOVE......................................................................................................................... 142#ERASE.......................................................................................................................... 142#HOSTAFT ..................................................................................................................... 143#START .......................................................................................................................... 144#PROMPT ..................................................................................................................... 146#DEFINENAME............................................................................................................. 148Labels............................................................................................................................ 151#IF.................................................................................................................................. 152#GOTO......................................................................................................................... 153#END............................................................................................................................. 154

Sample Scripts.................................................................................................................... 155Host Initiated Automatic File Transfer (HOSTAFT)................................................................ 159

Overview............................................................................................................................. 159

TABLE OF CONTENTS

IV

Monitoring HOSTAFT Status...............................................................................................160HOSTAFT Script Overview..................................................................................................160HOSTAFT Script Variable Substitution..............................................................................162Activating/Deactivating HOSTAFT on The PC ..............................................................162Activating A HOSTAFT Script for Processing ..................................................................163Activating A HOSTAFT Script In Batch ............................................................................163

VTAM Definitions for BIMFTRBC .................................................................................164CICS Definitions for BIMFTRBC...................................................................................165VSE JCL to Execute BIMFTRBC ..................................................................................166MVS JCL to Execute BIMFTRBC.................................................................................166Commands and Operands for BIMFTRBC..............................................................166

OPTION Command..............................................................................................167CONNECT Command .........................................................................................168HOSTAFT Command ............................................................................................169UPARM Command...............................................................................................171

Activating a HOSTAFT Script with a CICS Application ................................................172File Upload Scripts ....................................................................................................................174

Processing Options ............................................................................................................175#PROMPT.............................................................................................................................177Labels ...................................................................................................................................179#IF .........................................................................................................................................180#INCLUDE ............................................................................................................................181#GOTO ................................................................................................................................182data line ..............................................................................................................................183Variable Substitution .........................................................................................................183#END ....................................................................................................................................184Sample Script......................................................................................................................185

Host Customization using the FTRM Transaction.................................................................186Adding / Changing Definitions .......................................................................................187PF Key Summary.................................................................................................................189System Menu ......................................................................................................................190System Options Screen .....................................................................................................191Category Definition List.....................................................................................................194Category Definition Screen .............................................................................................195User Definition List...............................................................................................................200User Definition Screen .......................................................................................................201VSAM Profile List..................................................................................................................203VSAM Profile Definition Screen........................................................................................204SAM Profile List ....................................................................................................................209SAM Profile Definition Screen...........................................................................................210Script Definitions List ..........................................................................................................215Script Definition Screen.....................................................................................................216Dataset Access List............................................................................................................220Dataset Access Definition Screen ..................................................................................221Access Security Definitions...............................................................................................223

Access Level and Array Entries.................................................................................223Variable Substitution ..................................................................................................224Generic Masks .............................................................................................................224Processing Overview ..................................................................................................224Access Security Definitions (List)...............................................................................227Access Security Definitions for POWER....................................................................228Common Fields............................................................................................................228Access Security Definitions for EDIT..........................................................................231

TABLE OF CONTENTS

V

Access Security Definitions for Scripts..................................................................... 233Access Security Definitions for ICCF........................................................................ 234Access Security Definitions for LIBR ......................................................................... 236Access Security Definitions for JES........................................................................... 238Access Security Definitions for CICS Temporary Storage.................................... 240

HOSTAFT Status List ............................................................................................................ 242HOSTAFT Status Detail Screen ......................................................................................... 244

Special PF Keys ........................................................................................................... 244General Script Information Fields ............................................................................ 244Individual PC Status Fields ........................................................................................ 245

HOSTAFT Log Display Screen ........................................................................................... 248HOSTAFT Activate Script Screen..................................................................................... 249TCP/IP Connection Options ............................................................................................ 250

Viewing The Host Transfer Activity Log (FTRL)...................................................................... 251PF Key Summary ................................................................................................................ 252Transfer Activity Log Display............................................................................................ 253Transfer Event Display....................................................................................................... 259

Printing The Host Transfer Activity Log.................................................................................. 260Sample Report ................................................................................................................... 261Program BIMFTRPR............................................................................................................. 261VSE JCL to Execute BIMFTRPR ......................................................................................... 261MVS JCL to Execute BIMFTRPR........................................................................................ 262Commands and Operands for BIMFTRPR..................................................................... 262

Syntax ........................................................................................................................... 262PRINT Command ........................................................................................................ 263Field List Operands..................................................................................................... 264Field name Keywords ................................................................................................ 265Field name Relational Operators ............................................................................ 266(list) formats and rules................................................................................................ 266Rules for numbers as values...................................................................................... 266Rules for Date and Time values ............................................................................... 266Rules for strings as values .......................................................................................... 267Sample Print Commands.......................................................................................... 268

BIMFCV - File Conversion Utility ............................................................................................. 270Customizing BIMFCV......................................................................................................... 270

File Conversion Scripts............................................................................................................. 271Comments.......................................................................................................................... 272Processing Options ........................................................................................................... 273Field Definitions.................................................................................................................. 275Record Descriptions.......................................................................................................... 279#PROMPT ............................................................................................................................ 280Labels .................................................................................................................................. 282#IF......................................................................................................................................... 283#GOTO................................................................................................................................ 285#ERROR ............................................................................................................................... 286#GROUPBEG - Group Begin............................................................................................ 287#GROUPEND - Group End............................................................................................... 287#CRLF .................................................................................................................................. 290#INSERT Literal .................................................................................................................... 291#LINE.................................................................................................................................... 292#END.................................................................................................................................... 293#SKIP Record...................................................................................................................... 294Special Requirements for BIMFCV ................................................................................. 294

TABLE OF CONTENTS

VI

Putting it all together ........................................................................................................295(1) - A Simple Fixed Length Record File ..................................................................295(2) - A variable file containing multiple record types ..........................................297Files Containing a COBOL OCCURS DEPENDING ON clause.............................298

Processing ASCII Files.........................................................................................................301Character Strings ...............................................................................................................304Testing Your Script..............................................................................................................305

Driver Specifications.................................................................................................................306BIMFTRD$ - IND$ Driver (VSE Only) ..................................................................................307BIMFTRDB - VSE Library Driver (VSE/ESA 1.2 and above Only) ...................................310BIMFTRDC - VSAM Cluster Driver .....................................................................................315

IDCAMS Definitions .....................................................................................................322BIMFTRDD - Partitioned Dataset Driver (MVS Only) .....................................................328BIMFTRDE - BIM-EDIT Library Driver ..................................................................................330BIMFTRDF - BIM-EPIC and SAM Dataset Driver (VSE Only)..........................................337BIMFTRDI - ICCF Library Driver (VSE Only) ......................................................................345BIMFTRDJ - JES Access Driver (MVS Only) ......................................................................347BIMFTRDL - VSE Library Driver (VSE Only)........................................................................351BIMFTRDM - CICS Temporary Storage Access..............................................................354BIMFTRDP - POWER Queue Driver (VSE Only)................................................................356BIMFTRDQ - Sequential (QSAM) Dataset Driver (MVS Only) ......................................362BIMFTRDR - VSE Library Access Using BIM-EDIT (VSE Only)..........................................365BIMFTRDT - CICS Transient Data Upload Driver ............................................................368BIMFTRDV - VSAM Dataset Driver (Using Profiles).........................................................370BIMFTRDX - Script File Access...........................................................................................375

VSE/SP Interactive Interface ..................................................................................................377User Security Exits ......................................................................................................................379Format / Selection Exits............................................................................................................383Default Translate Tables ..........................................................................................................388

MESSAGES ...................................................................................................................................391BIMFCV Error Messages ...........................................................................................................393BIMFTR-7nn Error Messages .....................................................................................................394Messages From Host During Transfer.....................................................................................395FTRL Transaction Messages .....................................................................................................432FTRM Transaction Messages ...................................................................................................433BIMFTRBC Messages.................................................................................................................438BIMFTRLB Messages ..................................................................................................................439BIMFTRFI Messages ...................................................................................................................440BIMFTRPR Messages..................................................................................................................442BIMFTRxx-nnnn Messages ........................................................................................................443Allocation / Deallocation Errors .............................................................................................452EIBRESP Codes...........................................................................................................................455VSE XPCC Response Codes....................................................................................................456POWER XPCC Response Codes.............................................................................................457

APPENDIX A.................................................................................................................................459How To Code Commands (Syntax) ......................................................................................461

BIM-PC/TRANSFER INSTALLATION AND OPERATIONS GUIDE

Page 1

GETTING STARTED


Page 2 Introduction


Introduction Page 3

IntroductionBIM-PC/TRANSFER is a PC-Host File Transfer System that allows data to betransferred between any PC that is running a 3270 Emulator or an APPCinterface, and a host computer running CICS or BIM-TMAN.

HOST TO PCFILE

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 aTCP/IP connection be installed on the PC. Refer to the section “SystemRequirements” on page 16 for a list of the supported emulators and interfaces.

The following types of data can be transferred to and from the PC depending onyour 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)


Page 4 Introduction

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 jobstream, 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 separatelyfrom BIM.

• The PC-to-host connection can be LU2, APPC, or for VSE systems that haveTCP/IP for VSE from Connectivity Systems, a TCP/IP connection can beused.

• An on-line transaction (FTRM) is provided by BIM-PC/TRANSFER. This isused to define to the host the types of transfers that are to be supported, andwhich 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) isprovided for viewing this log. A Transfer Log can also be maintained at eachPC.

• All transfers can be secured on the host using signon authorization. Anextensive set of security options are available to limit access to host datasets,reports, and members to appropriate PC users. A user exit can also bewritten to perform security checks not normally supported by BIM-PC/TRANSFER.

• Transfers can be performed by request using the PC program BIMFTR(x), orcan be automated by using the PC program BIMAFT(x).

• PC program BIMFTR(x) performs transfers in response to a series of queriesand selections by the PC user.

• PC program BIMAFT(x) is an automated transfer program. This programuses a script that defines which transfers are to be performed. The scripts canbe constructed manually using the text editor within BIMAFT(x) or any otherPC text editor. The scripts can also be constructed using a 'record' feature ofBIMAFT(x).

• Data can be transferred in either EBCDIC or ASCII, with or without CRLFseparation.

• A script language is provided for both the PC and the Host for use during alldownloads. Scripts can be used for record selection and data formatconversions. The PC script can also be used for other file conversions.


Introduction Page 5

• A PC upload script can be used to concatenate PC files, and/or wrap hostJCL around files during uploads.


Page 6 Introduction

PC/TRANSFER OverviewThis section provides a brief overview of the transfer process on the PC. The PCprogram 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 informationregarding its operation. Refer to the section “Using The PC Transfer Program -BIMFTR(x)” on page 83 for a more detailed description of its use.

The PC program requires that a 3270 emulator, an APPC interface, or a TCP/IPinterface be running on the PC. The 3270 emulator must support the HLLAPIapplication interface. The APPC interface is not supported in DOS. The TCP/IPinterface is only supported in VSE.

If using a 3270 emulator, the PC user must establish a 3270 session with the CICSor BIM-TMAN on the mainframe side of BIM-PC/TRANSFER before starting thePC program. If you are using BIM-TMAN, you must also select transaction FTRTfrom the BIM-TMAN menu.

The PC user will be required to enter a userid and password each time the PCprogram is started.

File Transfer Debug Help

Selected Items

Available Items - 4 entries for Category POWER Queue Access

BIM-PC/TRANSFER - PC File Transfer (95/NT)

Upload... Download... Transfer... Accept... Accept All...Select all...

BIMDWDF.LST <-DNLD-- PWR,LST,BIMDWDF 143 LD3 1AUPTS2.LST <-DNLD-- PWR,LST,AUPTS2 5343 LD3 1ALANE2.FTS --UPLD-> EDIT,DDW ,ALANE2 FTSBIMDWDF.ASM <-DNLD-- EDIT,DDW ,BIMDWDF ASMBIMDWDG.ASM <-DNLD-- EDIT,DDW ,BIMDWDG ASM

BIMSPLTX 3968 QD3 1 CMPL 08/11/96 13:18:51 888 21BIMFTRSX 125 QD6 1 07/15/96 20:48:36 3258 74BIMFTRCM 130 QD6 1 07/15/96 20:40:42 2980 63BIMFTRDX 131 QD6 1 07/15/96 20:40:47 2092 53

Job Job Line Page Name Numbr Sfx CDP Rem S CC Form Date Time Count Count


Introduction Page 7

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 upperlist will fill in with the pending transfers. The lower list is filled in response to adownload query request.

Access to host files is based on what BIM-PC/TRANSFER refers to as “TransferCategories”. Categories define the type of information that can be transferred,and which PC users can have access to the information. A dialog similar to theone shown below is displayed when BIM-PC/TRANSFER needs to known whatcategory is desired for a specific transfer. The dialog will only contain thecategories that the specific PC user is authorized for.

The following dialogs show the categories as defined when BIM-PC/TRANSFERis installed the first time. Additional drivers are supplied to access other types ofhost data. Refer to section “Driver Specifications” on page 306 for a description ofall of the drivers supplied with BIM-PC/TRANSFER. New Category Definitionscan be added for these optional drivers by using the FTRM host transaction asdefine in section “Host Customization using the FTRM Transaction” starting onpage 186.

VSE:Host Access

BIM-EDIT Library AccessICCF Library Download AccessHost Transfer File Access (IND$)VSE Library Access (LIBR)POWER Queue AccessVSAM Dataset Access by ProfileVSAM Cluster Access

MVS:Host Access

BIM-EDIT Library AccessJES Queue AccessPartitioned Dataset AccessSequential Dataset AccessVSAM Dataset Access by ProfileVSAM Cluster Access

A download (from mainframe to PC) request is a multi-step process. First, youneed to select the mainframe category that you wish to download from, and thenyou will need to supply some selection criteria for that category. Once theselection criteria is set, this program will enter into a conversation with themainframe to obtain a list of available files for download purposes. The list ofavailable files is put into the lower list box in the main window. You can thenselect one or more files for download by clicking with the PC mouse on therelevant 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


Page 8 Introduction

will determine the category to upload the file into and fill out necessaryidentifying information specific to that category.

In neither case will the actual file transfer occur at this time. Instead, yourselection will be placed in the upper list box in the main window. You can reviewand/or change your selections prior to transfer by clicking with the PC mouse onthe appropriate selection entry. When you are ready to transfer data to or fromthe mainframe, select the transfer option from the File Menu. Both uploads anddownloads 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 anddownload operations. The sequence of appearance will differ somewhat as wellas the specific contents of the individual dialog box. The following is a step-by-step 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 todownload 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 mousebutton.

• You will be presented with a dialog asking you for selection criteria for theparticular category you have chosen. The selection fields, their contents andrequirements vary by category. Information is supplied in the Help Index forthose categories supplied by BIM.

• When you have made your selection entries, click on the “OK” button. Yourrequest will be sent to the host for resolution.

• The mainframe will review your selection criteria and return a list of filesmatching your entries. This file list will be placed in the lower of the two listboxes in the main window.

• When the mainframe process is completed, you can choose one or more filesfrom the list for download.

• When you choose a file for download, you will be presented with a dialogthat allows you to specify the PC file characteristics and transfer options.


Introduction Page 9

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 andselect a PC file for upload to the mainframe.

• Once you have selected the file, you will need to choose the mainframecategory to upload the file into. A list of available categories will bepresented.

• After selecting the category, you will need to supply identifying informationfor the mainframe. The information requirements vary according to thecategory you selected.

In each case, when the selection process is complete, the file will be placed in theupper list box. Transfer will not occur until you request it from the Transferoption on the File Menu.


Page 10 New For This Release

New for This ReleaseThis section highlights the new features that have been added to this release ofBIM-PC/TRANSFER. Detailed information on each of these features can befound in the remainder of this manual.

New for Release 1.8• New VSE Library Access has been provided via a new driver (BIMFTRDB).

Refer to section "BIMFTRDB - VSE Library Driver (VSE/ESA 1.2 and aboveOnly)" on page 310 for more information. This new driver requires VSE/ESA1.2 or above, but provides much better VSE Library support than driverBIMFTRDL.

• New IDCAMS Delete/Define support has been added to driver BIMFTRDC(VSE Only). Refer to section "BIMFTRDC - VSAM Cluster Driver" on page315 for more information.

• A new Automatic Transfer Script statement (#DEFINENAME) has beenadded. This statement can be used to generate PC file names using dataabout the file from information on the host. Refer to section"#DEFINENAME" on page 148 for more information.

• A new “Default Security Mode” has been added. Refer to section “Securityfor Transfers” on page 77 for more information.

New for Release 1.7• New SAM and BIM-EPIC managed dataset support has been added via a

new driver (BIMFTRDF). Refer to section "BIMFTRDF - BIM-EPIC and SAMDataset Driver (VSE Only)" on page 337 for more information.

• A new operand (OLEN=) has been added to the File Conversion Script fielddefinition. Refer to page 277 for more information.

• New "Connection Profiles" are supported in the 32-bit Windows versions ofthe PC program. Refer to section "Connection Profile Definitions" on page 43for more information.

• #PROMPT, #GOTO, #IF and @label statements have been added toAutomatic Transfer Scripts. Refer to section "Automatic Transfer Script" onpage 125 for more information.

• LU3270 Logoff Scripts are now supported. Refer to section "Logon/LogoffScripts" on page 69 for more information.

New for Release 1.6• 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 For This Release Page 11

• New VSAM Cluster Access Support via a new driver (BIMFTRDC). Refer tosection “BIMFTRDC - VSAM Cluster Driver” on page 315 for moreinformation.

• New CICS Temporary Storage Access Support via a new driver(BIMFTRDM). Refer to section “BIMFTRDM - CICS Temporary StorageAccess” on page 354 for more information.

• Most drivers now support the specification of a generic “LIBQUE” whichwill generate a new dialog on the PC containing the matching LIBQUEvalues. The PC user than selects the requested LIBQUE from this new dialog.Refer to sections “Generic LIBQUE Values for Downloads” on page 98 and“Generic LIBQUE Values for Uploads” on page 102 for more information.

• The BIM-EDIT driver has been expanded to provide access to BIM-EDIT mailitems. Refer to section “BIMFTRDE - BIM-EDIT Library Driver” on page 330for more information.

New for Release 1.5• 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 aLogon Script. Refer to section “Logon/Logoff Scripts” on page 69 for moreinformation.

• The security controls for access to host data has been greatly enhanced. Referto the new section “Access Security Definitions” on page 223.

• Increased transfer rates are now possible with LU2/3270 connections whenusing certain emulators. Refer to field “Struct. Fields” on page 48 for moreinformation.

• A new Automatic Transfer script command “#START” has been added. Thiscan be used to started transactions on the host when a transfer has beencompleted. Refer to page 144 for more information.

• Two new dialogs have been added to the PC program for downloadprocessing. They are used to specify defaults for download processingoptions, and to override individual download processing options as eachtransfer is requested. Refer to “Defaults Button” on page 99, and “CategoryOptions Button” on page 101 for more information.

• The method for specifying the “Download Script Name” on the PC haschanged for most transfer categories. Refer to section “Download ScriptName” on page 99 for more information.

New for Release 1.4• A new Host Initiated Automatic File Transfer feature (HOSTAFT) has been

added. This allows host programs and/or applications to control when filetransfers occur to and from PC’s. Refer to section “Host Initiated AutomaticFile Transfer (HOSTAFT) starting on page 159 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


Page 12 New For This Release

with its own security, viewing and/or updating authority. Refer to section“ALT MAINT TXN CODES” on page 192 for more information.

New for Release 1.3• “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 TheHost Transfer Activity Log (FTRL)” on page 251 , section “VSE InstallationStep 5 - Define Host Activity Log File” on page 22 , and section “MVSInstallation Step 5 - Define Host Activity Log File” on page 33 .

• Support for remote VSAM dataset access in CICS has been added. Refer tothe section “Remote Files in CICS” on page 371.

• Support for “replacing” VSAM datasets defined with the REUSE option hasbeen added. Refer to the “EMPTY” driver data option on page 374.


Migration Requirements Page 13

Migration RequirementsThe following sections cover the changes in the installation and use ofBIM-PC/TRANSFER that may be required if you are migrating from an earlierrelease.

Changes from Release 1.7• The "TCP/IP for VSE" interface has been redesigned in anticipation of future

interfaces being added. The common TCP/IP for VSE logic as been moved toa new module (BIMFTR92). If you are currently using this interface, youmust add this new module to the CICS PPT or RDO as described in theInstallation Section “VSE Installation Step 6 - CICS/VS Table Additions” onpage 23.

• If you plan on using the new VSE Library Access driver (BIMFTRDB), it mustbe added to the CICS PPT or RDO as described in the Installation Section“VSE Installation Step 6 - CICS/VS Table Additions” on page 23.

• If you plan on using the new IDCAMS Delete/Define support that has beenadded to driver BIMFTRDC (VSE Only), you will need to add a new entryfor program (BIMFTR98) to your CICS PPT or RDO as described in theInstallation Section “VSE Installation Step 6 - CICS/VS Table Additions” onpage 23.

Changes from Release 1.6• If you plan on using the new SAM and/or BIM-EPIC dataset support, the

new Driver (BIMFTRDF) and BIM-EPIC interface module (BIMEPACC) mustbe added to the CICS PPT or RDO as described in the Installation Section“VSE Installation Step 6 - CICS/VS Table Additions” on page 23.

Changes from Release 1.5• 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 CICSPPT or RDO as described in the Installation Section.

• If you plan on using the new TCP/IP interface, you will need to adddefinitions for programs BIMFTRI2 and BIMFTRIP and transactions FTRIand FTRP as described in the Installation Section. There is also a newinstallation step “VSE Installation Step 9 - Activating the TCP/IP Interface”described on page 26.

Changes from Release 1.4• No installation changes required.


Page 14 Migration Requirements

• You may want to make use of the new security controls for access to hostdata. Refer to the new section “Access Security Definitions” on page 223.

• Two new dialogs have been added to the PC program for downloadprocessing. They are used to specify defaults for download processingoptions, and to override individual download processing options as eachtransfer is requested. Refer to “Defaults Button” on page 99, and “CategoryOptions Button” on page 101 for more information.

• The method for specifying the “Download Script Name” on the PC haschanged for most transfer categories. Refer to section “Download ScriptName” on page 99 for more information.

Changes from Release 1.3• A new module (BIMFTRHC) must be added to your CICS definitions. It is

required for HOSTAFT processing. Refer to the section “VSE Installation Step6 - CICS/VS Table Additions” on page 23 and section “MVS Installation Step6 - CICS/VS Table Additions” on page 34.

• If you will be using the new HOSTAFT feature, you may need to increase thesize of your BIM-PC/TRANSFER Host Control File. Additional records areadded and maintained on the control file for each HOSTAFT Script that isactivated for processing.

Changes from Release 1.2• “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 isrequired for VSAM transfers. Refer to the section “VSE Installation Step 6 -CICS/VS Table Additions” on page 23 and section “MVS Installation Step 6 -CICS/VS Table Additions” on page 34.

• A new host activity log has been added. Refer to the sections “Viewing TheHost Transfer Activity Log (FTRL)” on page 251 , section “VSE InstallationStep 5 - Define Host Activity Log File” on page 22 , and section “MVSInstallation Step 5 - Define Host Activity Log File” on page 33.

This new feature also requires a new CICS transaction (FTRL) and two newprograms (BIMFTRL and BIMFTRLD). Refer to the section “VSE InstallationStep 6 - CICS/VS Table Additions” on page 23 and section “MVS InstallationStep 6 - CICS/VS Table Additions” on page 34.

Changes from Release 1.1 (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-TMANrelease 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 21for the new IDCAMS define parameters. A conversion program has been


Migration Requirements Page 15

provided to convert your existing control file to the new format. To convertyour 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 APPCinterface. Refer to “VSE Installation Step 6 - CICS/VS Table Additions” onpage 23 for the CICS definition required for this new module.


Page 16 System Requirements

System RequirementsBIM-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, 5.2.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, andmost recent releases of VSE, MVS/XA and MVS/ESA.

The IND$ interface of BIM-PC/TRANSFER will only function on CICS/VSE 2.2and above. It also requires a 3270 connection. It will not function with an APPCconnection.

The BIM-EDIT interface of BIM-PC/TRANSFER requires that the host system berunning release 5.0A or above of BIM-EDIT.

The BIM-EPIC managed dataset support requires BIM-EPIC release 6.1B at PTFlevel EP61B041 or above.

The VSE Library Access driver BIMFTRDB requires VSE/ESA 1.2 or above. Ifyou are on an older release of VSE, use driver BIMFTRDL for VSE LibraryAccess.

Four versions of the PC program are provided:

1) a 32-bit version for Microsoft Windows 95/98 or NT2) a 16-bit version for Microsoft Windows 3.13) a 32-bit version for OS/24) 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 longas you are using a 3270 or APPC emulator that provides a 16-bit HLLAPIinterface.

The 32-bit Windows 95/98/NT version requires a 3270 or APPC emulator thatprovides a 32-bit HLLAPI interface.


System Requirements Page 17

Supported LU2/3270 Interfaces:

The following PC 3270 emulators have been tested with the 32-bit Windows95/98/NT version of BIM-PC/TRANSFER:

• 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 Windowsversion 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 ofBIM-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 ofBIM-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 HLLAPIapplication interface as documented by IBM.

Supported APPC Interfaces:

The following APPC interfaces have been tested with the 32-bit Windows95/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 versionof BIM-PC/TRANSFER:

• IRMA Workstation for Windows®• RUMBA® APPC Client• DynaComm/Elite®


Page 18 System Requirements

• IBM Personal Communications PC/3270®

The following APPC interfaces have been tested with the OS/2 version ofBIM-PC/TRANSFER:• Communications Manager/2® from IBM

All of the above APPC interfaces have been tested using a token-ring connectionto 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 VSEhost running TCP/IP for VSE from Connectivity Systems. Other interfaces maybe added in future releases.


Installation for VSE Page 19

Installation for a VSE HostBIM-PC/TRANSFER/VSE is shipped on an unlabeled tape or cartridgecontaining 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 yourlibraries:

Load/object Library

BIMFTR92 TCP/IP for VSE interface routinesBIMFTR98 IDCAMS Command processor used by BIMFTRDCBIMFTR99 FTRT common subroutineBIMFTRBC Batch command interface for HOSTAFTBIMFTRCM FTRT command processingBIMFTRD$ FTRT driver for IND$ accessBIMFTRDB FTRT driver for VSE Library (LIBR) access (ESA 1.2+)BIMFTRDC FTRT driver for VSAM Cluster accessBIMFTRDE FTRT driver for BIM-EDIT accessBIMFTRDF FTRT driver for SAM and BIM-EPIC dataset accessBIMFTRDI FTRT driver for ICCF accessBIMFTRDL FTRT driver for VSE Library (LIBR) accessBIMFTRDM FTRT driver for CICS Temporary StorageBIMFTRDP FTRT driver for POWER accessBIMFTRDR FTRT driver for VSE Library access via BIM-EDITBIMFTRDT FTRT driver for CICS Transient Data uploadsBIMFTRDV FTRT driver for VSAM dataset accessBIMFTRDX FTRT driver for script dataset accessBIMFTRFC Control file conversion from release 1.1 formatBIMFTRFI Control file initializationBIMFTRFT Host customizationBIMFTRHC HOSTAFT application/command interfaceBIMFTRI1 FTRT input processingBIMFTRI2 FTRI input processing for TCP/IPBIMFTRIP TCP/IP started taskBIMFTRL Activity log display mapsetBIMFTRLB LIBR server for Driver BIMFTRDLBIMFTRLD Activity log displayBIMFTRM Customization program mapsetBIMFTROD FTRT output processingBIMFTRPR Activity log print programBIMFTRSM Service module for VSAM dataset accessBIMFTRTT EBCIDIC/ASCII translate tableBIMFTRXP FTRT script processingBIML62CI APPC interface programBIMXMC00 Host module used by BIMFTRDL LIBR interface


Page 20 Installation for VSE

BIMXPC00 Host module used by POWER XPCC interfaceBIUAPMD Host module used by BIM-EDIT interfaceBIULUMD Host module used by BIM-EDIT LU 6.2 interfaceBIMFTRPW.OBJ Password encode/decode for exit programs

Source LibraryBIMFTRDS.E Customization macro for exit programsBIMFTRFX.A Sample formatting/selection exitBIMFTRHC.A HOSTAFT application COMMAREA for AssemblerBIMFTRHC.C HOSTAFT application COMMAREA for COBOLBIMFTRSX.A Sample security exitBIMFTRJ1.A Job to define/initialize the host control file BIMFTRFBIMFTRJ2.A Job to define/initialize the host activity log BIMFTRLBIMFTRJ3.A Job to define the required CICS RDO entriesBIMFTRS1.A Sample CICS FCT entries

VSE Installation Step 1 - Load Distribution Tape

Mount the distribution tape on a tape drive and enter the followingPOWER/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 apartition 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 containBIM-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.



VSE Installation Step 4 - Define the Host Control File

The Host side of BIM-PC/TRANSFER requires a VSAM KSDS control file that isused to define the types of transfers that are allowed, and optionally, who canperform 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 (100100) should work fine for most installations, unless you have a large number ofusers you will be defining, or will be using the HOSTAFT feature extensively.

Define and initialize the control file using the following jobstream. This jobstreamis provided in source member BIMFTRJ1.A:

// JOB INIT* STEP 1 - DEFINE CONTROL FILE// EXEC IDCAMS DEFINE CLUSTER ( - NAME(BIMPCTFR.CONTROL.FILE) - RECORDS(100 100) - KEYS(64 0) - NOREUSE - FREESPACE(15 10) - RECORDSIZE(256 4089) - 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=AUTOINITIALIZE CONTROLFILE/&

The initialization program in step 2 (BIMFTRFI) will define a CATEGORY recordfor 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



VSE Installation Step 5 - Define Host Activity Log File

The Host side of BIM-PC/TRANSFER can optionally maintain a transfer activitylog. This log requires a VSAM RRDS file.

Define and initialize the activity log file using the following jobstream. Thisjobstream 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(584 584) - 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=AUTOINITIALIZE LOGFILE/&

The initialization program in step 2 (BIMFTRFI) will format the log file. Eachtransfer requires two log records. One when the transfer starts, and one when itcompletes. Specify the RECORDS operand with the number of events that youwant to maintain in the log file. The log file is a ‘wrap-around’ file. Once the fileis 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 theexisting log file to the new file using an IDCAMs REPRO, and executing step 2 ofthe above jobstream to re-initialize the new file. The initialize step will detect thatit is an existing file, and update the control record to account for the expandedsize.

Remember to add the following DLBL to your CICS or BIM-TMAN startup JCL:

// DLBL BIMFTRL,'BIMPCTFR.LOG.FILE',,VSAM



VSE Installation Step 6 - CICS/VS Table Additions

The following entries are required in the CICS that will be used for the Host sideof BIM-PC/TRANSFER. Omit this step if you will be using BIM-TMAN insteadof 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=ALTERNATEDFHPCT TYPE=ENTRY,TRANSID=FTRL,PROGRAM=BIMFTRLD, X SCRNSZE=ALTERNATEDFHPCT TYPE=ENTRY,TRANSID=FTRI,PROGRAM=BIMFTRI2 (note 5)DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRI1DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRI2 (note 5)DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRIP (note 5)DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRODDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRCMDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRFTDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRLDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRLDDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRMDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRD$DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDBDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDCDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDEDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDFDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDIDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDLDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDMDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDPDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDTDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDRDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDVDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDXDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRHCDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRSM (note 2)DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRXPDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRTTDFHPPT TYPE=ENTRY,PROGRAM=BIMFTR92 (note 5)DFHPPT TYPE=ENTRY,PROGRAM=BIMFTR98DFHPPT TYPE=ENTRY,PROGRAM=BIMFTR99DFHPPT TYPE=ENTRY,PROGRAM=BIML62CIDFHPPT TYPE=ENTRY,PROGRAM=BIMEPACC (note 6)



If you are using RDO, make the following definitions. A jobstream to performthis 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(BIMFTRDB) 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(BIMFTR92) LANG(A) (note 5)CEDA DEFINE GROUP(FTR) PROG(BIMFTR98) 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: If you change the transaction id FTRT to some other value, you mustalso change the PC programs INI files (BIMFTR.INI andBIMAFT.INI). Find the line in each INI that reads: TRANSACTIONFTRT, and change the FTRT to the new value you have selected.

Note 2: If you want to access a VSAM dataset in a remote CICS system, youmust define a program/PPT entry for module BIMFTRSM in theCICS system that owns the dataset.

Note 3: The TWASIZE operand is only required if you intend to use the VSEHost Transfer (IND$) interface.

Note 4: You can define up to 4 alternate transactions for use in viewing andcustomizing the Host Control File. Refer to “ALT MAINT TXNCODES” on page 192 for more information.

Note 5: The entries for FTRI, FTRP, BIMFTRI2, BIMFTRIP and BIMFTR92are only required if you plan to use TCP/IP connections.

Note 6: The entry for BIMEPACC is only required if you plan to transferBIM-EPIC managed datasets using driver BIMFTRDF. This moduleis shipped with the BIM-EPIC product.



Add the following FCT entry for the BIM-PC/TRANSFER Control File. This isprovided 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 thefollowing 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 betransferred to and from PC’s by specifying their cluster name. This featurerequires one or more ‘generic’ FCT entries that BIM-PC/TRANSFER willtemporarily use during the actual transfers. Refer to section “Cluster NameTransfer Feature” on page 205 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 suchas CICS PPT entries. You can ignore any reference in this manual to programdefinitions if you are only using BIM-TMAN.

The entries for FTRI and FTRP are only required if you will be using TCP/IPconnections between your PCs and the host.



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 MAINTTXN CODES” on page 192 for more information.

Except for the FILE operands for BIMFTRF and BIMFTRL shown above, you willonly need to provide additional FILE operands for the following types of VSAMdatasets:

1) Datasets defined in VSAM profiles that you need to upload into. You do notneed FILE operands for datasets transferred using the “Cluster NameTransfer Feature” described on page 205.

2) 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 datasetaccess dataset access type

I = input only (default)U = updateL = load mode

strno VSAM number of strings (default is 3)type VSAM cluster type

KS = Keyed SequenceES = Entry SequenceRR = Relative Record

BIM-TMAN also requires that DLBLs be present for all VSAM datasets to beaccessed, 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 severalCATEGORY definitions for your initial use. These default definitions will allowmost installations to begin using BIM-PC/TRANSFER immediately. To reviewthese definitions, bring up the CICS or BIM-TMAN system containing the abovedefinitions, and use the FTRM transaction. CATEGORY definitions are used todefine which transfers are allowed using BIM-PC/TRANSFER. Refer to thesection “Host Customization using the FTRM Transaction” on page 186 for moreinformation.

VSE Installation Step 9 - Activating the TCP/IP Interface

Skip this step if you will not be using TCP/IP connections between the host andyour PCs.



Before performing this step, review section “TCP/IP Connection Options” onpage 250.

If you are running BIM-PC/TRANSFER in CICS, add the following entry to yourCICS startup and shutdown PLTs:

DFHPLT TYPE=ENTRY,PROGRAM=BIMFTRIP

If you are running BIM-PC/TRANSFER in BIM-TMAN, add the followingoperand to the BIM-TMAN DEFINE command in your startup JCL:

STARTUP(FTRP) -

The value specified for ‘FTRP” must match the tranid defined for programBIMFTRIP.

VSE Installation Step 10 - PC Program Installation

Install the PC program on the PCs that will be transferring data. You may haveseveral diskettes depending on which versions of the PC software you haveordered.

The section “Connecting the PC to the Host” on page 41 contains information foractivating 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 ofBIM-PC/TRANSFER in a drive on your PC. Click the “Start” button, and selectthe “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 installationdiskette.

VSE Installation Step 10b - Microsoft Windows 3.1, 3.11, and NT 3.5.1

Insert the installation diskette containing the Windows or Windows NT versionof BIM-PC/TRANSFER in a drive on your PC. Select “Run” from the ProgramManagers “File” menu and enter the following command in the RUN dialog box:

A:SETUP.EXE




VSE Installation Step 10c - PC Program for OS/2

Insert the installation diskette containing the OS/2 version of BIM-PC/TRANSFER in a drive on your PC and enter the following at an OS/2command line:

A:INSTALL

-or-

A:INSTALL /T:path

where A: is the diskette drive containing the BIM-PC/TRANSFER PC installationdiskette, and “path” is the drive and directory into which you want BIM-PC/TRANSFER installed. The default path is “C:\BIMFTR”.

VSE Installation Step 10d - PC Program for DOS

Please review the “BIM-PC/TRANSFER Copyright Notice” on the back side ofthe cover page of this manual before installing the DOS version.

Insert the BIM-PC/TRANSFER PC diskette containing the DOS version into adrive, and enter the following commands:

MD bimftrCD bimftrA:INSTALL A:

where A: is the diskette drive containing the BIM-PC/TRANSFER PC installationdiskette, and 'bimftr' is the directory you want to install the software into.

VSE Installation Step 10e - PC Program README File

The PC diskettes contain a README file with information not available whenthis manual was printed. This file contains technical information about using andinstalling the PC software with various 3270 and APPC emulators.


Installation for MVS Page 29

Installation for a MVS HostBIM-PC/TRANSFER/MVS is shipped on a labeled tape or cartridge containingtwo datasets created by IEBCOPY. The first dataset contains pre-generated loadmodules to be transferred to your Load Library. The second dataset containssample source and macros to be transferred to your Source Library.

Load Library Modules

BIMFTR99 FTRT common subroutineBIMFTRBC Batch command interface for HOSTAFTBIMFTRCM FTRT command processingBIMFTRDC FTRT driver for VSAM Cluster accessBIMFTRDD FTRT driver for PDS accessBIMFTRDE FTRT driver for BIM-EDIT accessBIMFTRDJ FTRT driver for JES accessBIMFTRDM FTRT driver for CICS Temporary StorageBIMFTRDQ FTRT driver for QSAM accessBIMFTRDT FTRT driver for CICS Transient Data uploadsBIMFTRDV FTRT driver for VSAM dataset accessBIMFTRDX FTRT driver for script dataset accessBIMFTRFI Control file initializationBIMFTRFT Host customizationBIMFTRHC HOSTAFT application/command interfaceBIMFTRI1 FTRT input processingBIMFTRL Activity log display mapsetBIMFTRLD Activity log displayBIMFTRM Host customization program mapsetBIMFTROD FTRT output processingBIMFTRPR Activity log print programBIMFTRPW Password encode/decode for exit programsBIMFTRSM Service module for VSAM dataset accessBIMFTRTT EBCIDIC/ASCII translate tableBIMFTRXP FTRT script processingBIMGETOF JES interface offset tableBIMGETSP JES interface moduleBIML62CI APPC interface programIGC0024I SVC for JES and BIM-EDIT access

Source Library ModulesBIMFTRDS Customization macro for exit programsBIMFTRFX Sample formatting/selection exitBIMFTRHA HOSTAFT application COMMAREA for AssemblerBIMFTRHC HOSTAFT application COMMAREA for COBOLBIMFTRSX Sample security exit


Page 30 Installation for MVS

BIMFTRJ1 Job to define/initialize the host control file BIMFTRFBIMFTRJ2 Job to define/initialize the host activity log BIMFTRLBIMFTRJ3 Job to define the required CICS RDO entriesBIMFTRJ4 Job to generate JES interface offset tableBIMFTRS1 Sample CICS FCT entriesBIMGETOF Macro to generate JES interface offset table

MVS Installation Step 1 - Load Distribution Tape

Create the following JCL which will load the distribution tape to your Source andLoad Libraries.

//JOBID JOB (accounting),'LOAD BIMPCFTR',// CLASS=A,MSGCLASS=*,MSGLEVEL=(1,1)//*//* LOAD BIM-PC/TRANSFER DISTRIBUTION TAPE//*//IEBCOPY EXEC PGM=IEBCOPY//SYSPRINT DD SYSOUT=*//TAPEF1 DD DSN=BIMPCTFR.LOADLIB,UNIT=TAPE,DISP=OLD,// LABEL=(1,SL),VOL=(,RETAIN,SER=BIMSYS)//TAPEF2 DD DSN=BIMPCTFR.SOURCE,UNIT=TAPE,DISP=OLD,// LABEL=(2,SL),VOL=REF=*.TAPEF1//LOADLIB DD DSN=your.loadlib,DISP=SHR//SRCELIB DD DSN=your.sourclib,DISP=SHR//SYSIN DD * COPY I=((TAPEF1,R)),O=LOADLIB COPY I=((TAPEF2,R)),O=SRCELIB/*//

MVS Installation Step 2 - Install SVC

The JES and BIM-EDIT interfaces of BIM-PC/TRANSFER requires an SVC to beinstalled in your MVS system. If you do not wish to use these interfaces, you canskip this step.

If you are running a BIM-EDIT release above 5.0C, this SVC is already installed.You will need to know the SVC number assigned during the BIM-EDITinstallation. If it is other than 249, you will need to customize BIM-PC/TRANSFER. Refer to the section “Driver Specifications” starting on page 306for information on customizing drivers BIMFTRDE and BIMFTRDJ.

If you are running BIM-EDIT 5.0C or below, you can either replace the SVC usedby BIM-EDIT with the SVC on this distribution tape, or you can assign a newSVC number for use by BIM-PC/TRANSFER.

The following steps should be followed to install the SVC:

1) The SVC is shipped for a default number of 249. If this SVC number isalready used in your system, you will need to rename the load module(IGC0024I) for the SVC. The 24I in the name is the SVC number, with the “I”being a “zoned 9”.



2) Copy the SVC load module (IGC0024I) from the BIM-PC/TRANSFER loadlibrary to library SYS1.LPALIB. For MVS/ESA, you can copy this module toone of your own site LPA libraries instead.

3) Add one of the following statements to member IEASVCnn (where nn is atwo-digit number) in library SYS1.PARMLIB:

SVCPARM 249,REPLACE,TYPE(3),EPNAME(IGC0024I),APF(NO) - or -SVCPARM 249,REPLACE,TYPE(4),EPNAME(IGC0024I),APF(NO)

4) Add one of the following statements to member IEAFIXnn (where nn is atwo-digit number) in library SYS1.PARMLIB:

MVS: SYS1.LPALIB IGC0024I

MVS/ESA: INCLUDE LIBRARY(your.site.lpalib) MODULE(IGC0024I)

5) Add the following statement to member IEASYSnn (where nn is a two-digitnumber) in library SYS1.PARMLIB:

FIX=(nn,NOPROT)

where nn is a two-digit number identifying the nn suffix of memberIEAFIXnn mentioned above.

6) If you used and SVC number other than 249, you will need to customizeBIM-PC/TRANSFER. Refer to the section “Driver Specifications” starting onpage 306 for information on customizing drivers BIMFTRDE and BIMFTRDJ.

MVS Installation Step 3 - Customize JES Interface

The JES interface of BIM-PC/TRANSFER requires a special module (BIMGETOF)to be generated at each MVS site. This module contains information about yourspecific release of JES. It is generated using your JES source library as input, anda macro provided on the BIM-PC/TRANSFER distribution tape.

If you will not be using the JES interface of BIM-PC/TRANSFER, you can skipthis step, otherwise modify as needed the following JCL and submit it to generatethe interface module. This jobstream is provided in source member BIMFTRJ4.



//JOBID JOB (accounting),'GEN BIMGETOF',// CLASS=A,MSGCLASS=*,MSGLEVEL=(1,1)//*//* GENERATE BIM-PC/TRANSFER BIMGETOF MODULE//*//ASM EXEC PGM=IEV90,REGION=2048K,// PARM='TERM,XREF(SHORT),LOAD,NODECK,SYSPARM(SP 5.1)'//SYSTERM DD SYSOUT=*//SYSPRINT DD SYSOUT=*//SYSUT1 DD UNIT=SYSDA,SPACE=(CYL,(2,2))//SYSUT2 DD UNIT=SYSDA,SPACE=(CYL,(2,2))//SYSUT3 DD UNIT=SYSDA,SPACE=(CYL,(2,2))//SYSLIN DD DSN=&&OBJSET,UNIT=SYSDA,SPACE=(80,(2000,100)),// DISP=(MOD,PASS)//SYSLIB DD DISP=SHR,DSN=SYS1.HASPSRC <==JES SOURCE// DD DISP=SHR,DSN=SYS1.MACLIB// DD DISP=SHR,DSN=SYS1.MODGEN// DD DISP=SHR,DSN=SYS1.AMODGEN//SYSIN DD DISP=SHR,DSN=bimpcftr.source(BIMGETOF)/*//LNK EXEC PGM=IEWL,PARM='XREF,LET,LIST',// COND=(7,LT,ASM)//SYSLIN DD DSN=&&OBJSET,DISP=(OLD,DELETE)//SYSLMOD DD DISP=SHR,DSN=bimpcftr.loadlib(BIMGETOF)//SYSUT1 DD UNIT=SYSDA,SPACE=(1024,(100,10))//SYSPRINT DD SYSOUT=*//

The SYSPARM(SP 5.1) on the ASM step must be set to the release of JES thatyou are running.

Important Note:

You will need to re-generate this module every time you apply IBMmaintenance to your JES system, or when installing a new release of JES.

MVS Installation Step 4 - Define the Host Control File

The Host side of BIM-PC/TRANSFER requires a VSAM KSDS control file that isused to define the types of transfers that are allowed, and optionally, who canperform 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 (100100) should work fine for most installations, unless you have a large number ofusers you will be defining, or will be using the HOSTAFT feature extensively.



Define and initialize the control file using the following jobstream. This jobstreamis provided in source member BIMFTRJ1:

//jobname JOB//* STEP 1 - DEFINE CONTROL FILE//STEP1 EXEC PGM=IDCAMS//SYSPRINT DD SYSOUT=*//SYSIN DD * DEFINE CLUSTER ( - NAME(BIMPCTFR.CONTROL.FILE) - RECORDS(100 100) - KEYS(64 0) - NOREUSE - FREESPACE(15 10) - RECORDSIZE(256 4089) - SHAREOPTIONS(4) - SPEED - VOLUMES(vvvvvv) - ) - DATA ( - NAME(BIMPCTFR.CONTROL.FILE.DATA) - CISZ(8192) - ) - INDEX ( - NAME(BIMPCTFR.CONTROL.FILE.INDEX) - )/*//STEP2 EXEC PGM=BIMFTRFI//STEPLIB DD DSN=bimpctfr.loadlib,DISP=SHR//BIMFTRF DD DSN=BIMPCTFR.CONTROL.FILE,DISP=SHR//SYSIN DD *INITIALIZE CONTROLFILE//SYSPRINT DD SYSOUT=*//

The initialization program in step 2 (BIMFTRFI) will define a CATEGORY recordfor 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 DD to your CICS or BIM-TMAN startup JCL:

//BIMFTRF DD DSN=BIMPCTFR.CONTROL.FILE,DISP=SHR

MVS Installation Step 5 - Define Host Activity Log File

The Host side of BIM-PC/TRANSFER can optionally maintain a transfer activitylog. This log requires a VSAM RRDS file.



Define and initialize the activity log file using the following jobstream. Thisjobstream is provided in source member BIMFTRJ2:

//jobname JOB//* STEP 1 - DEFINE ACTIVITY LOG FILE//STEP1 EXEC PGM=IDCAMS//SYSPRINT DD SYSOUT=*//SYSIN DD * DEFINE CLUSTER ( - NAME(BIMPCTFR.LOG.FILE) - RECORDS(100) - NOREUSE - NUMBERED - RECORDSIZE(584 584) - SPEED - VOLUMES(vvvvvv) - ) - DATA ( - NAME(BIMPCTFR.LOG.FILE.DATA) - CISZ(4096) - )/*//STEP2 EXEC PGM=BIMFTRFI//STEPLIB DD DSN=bimpctfr.loadlib,DISP=SHR//BIMFTRL DD DSN=BIMPCTFR.LOG.FILE,DISP=SHR//SYSIN DD *INITIALIZE LOGFILE//SYSPRINT DD SYSOUT=*///&

The initialization program in step 2 (BIMFTRFI) will format the log file. Eachtransfer requires two log records. One when the transfer starts, and one when itcompletes. Specify the RECORDS operand with the number of events that youwant to maintain in the log file. The log file is a ‘wrap-around’ file. Once the fileis 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 theexisting log file to the new file using an IDCAMs REPRO, and executing step 2 ofthe above jobstream to re-initialize the new file. The initialize step will detect thatit is an existing file, and update the control record to account for the expandedsize.

Remember to add the following DD to your CICS or BIM-TMAN startup JCL:

//BIMFTRL DD DSN=BIMPCTFR.LOG.FILE,DISP=SHR

MVS Installation Step 6 - CICS/VS Table Additions

The following entries are required in the CICS that will be used for the Host sideof BIM-PC/TRANSFER. Omit this step if you will be using BIM-TMAN insteadof CICS.



DFHPCT TYPE=ENTRY,TRANSID=FTRT,PROGRAM=BIMFTRI1, X (note 1) SCRNSZE=ALTERNATEDFHPCT TYPE=ENTRY,TRANSID=FTRM,PROGRAM=BIMFTRFT, X (note 3) SCRNSZE=ALTERNATEDFHPCT TYPE=ENTRY,TRANSID=FTRL,PROGRAM=BIMFTRLD, X SCRNSZE=ALTERNATEDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRCMDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDCDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDDDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDEDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDJDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDMDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDQDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDTDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDVDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDXDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRFTDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRHCDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRI1DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRLDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRLDDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRMDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRODDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRTTDFHPPT TYPE=ENTRY,PROGRAM=BIMFTRSM (note 2)DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRXPDFHPPT TYPE=ENTRY,PROGRAM=BIMFTR99DFHPPT TYPE=ENTRY,PROGRAM=BIMGETSPDFHPPT TYPE=ENTRY,PROGRAM=BIMGETOFDFHPPT TYPE=ENTRY,PROGRAM=BIML62CI

If you are using RDO, make the following definitions. A jobstream to performthis is provided in source member BIMFTRJ3. The source member also containsDEFINEs for the required datasets described below.

CEDA DEFINE GROUP(FTR) PROF(FTRALT) SCRNSIZE(ALT) UCTRAN(No)CEDA DEFINE GROUP(FTR) PROG(BIMFTRCM) LANG(A)CEDA DEFINE GROUP(FTR) PROG(BIMFTRDC) LANG(A)CEDA DEFINE GROUP(FTR) PROG(BIMFTRDD) LANG(A)CEDA DEFINE GROUP(FTR) PROG(BIMFTRDE) LANG(A)CEDA DEFINE GROUP(FTR) PROG(BIMFTRDJ) LANG(A)CEDA DEFINE GROUP(FTR) PROG(BIMFTRDM) LANG(A)CEDA DEFINE GROUP(FTR) PROG(BIMFTRDQ) LANG(A)CEDA DEFINE GROUP(FTR) PROG(BIMFTRDT) 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(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(BIMGETSP) LANG(A)CEDA DEFINE GROUP(FTR) PROG(BIMGETOF) LANG(A)CEDA DEFINE GROUP(FTR) PROG(BIML62CI) LANG(A)CEDA DEFINE GROUP(FTR) TRAN(FTRM) PROG(BIMFTRFT) PROF(FTRALT) (note 3)CEDA DEFINE GROUP(FTR) TRAN(FTRL) PROG(BIMFTRLD) PROF(FTRALT)CEDA DEFINE GROUP(FTR) TRAN(FTRT) PROG(BIMFTRI1) PROF(FTRALT) (note 1)

Note 1: If you change the transaction id FTRT to some other value, youmust also change the PC programs INI files (BIMFTR.INI andBIMAFT.INI). Find the line in each INI that reads: TRANSACTIONFTRT, and change the FTRT to the new value you have selected.



Note 2: If you want to access a VSAM dataset in a remote CICS system, youmust define a program/PPT entry for module BIMFTRSM in theCICS system that owns the dataset.

Note 3: You can define up to 4 alternate transactions for use in viewing andcustomizing the Host Control File. Refer to “ALT MAINT TXNCODES” on page 192 for more information.

If you are using CICS 3.3 or above, the following RDO operands must bespecified, or allowed to default for all of the above definitions:

TRANSACTION TASKDATAKEY(USER) TASKDATALOC(BELOW)

PROGRAM EXECKEY(USER) DATALOCATION(BELOW)

If you are using CICS 4.1 or above, and have "Storage Protection" active, thefollowing RDO operands must be specified:

TRANSACTION TASKDATAKEY(CICS) TASKDATALOC(BELOW)

PROGRAM EXECKEY(CICS) DATALOCATION(BELOW)

Add the following FCT entry for the BIM-PC/TRANSFER Control File. This isprovided in source member BIMFTRS1:

DFHFCT TYPE=FILE,FILE=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 are using RDO to define the control file, use the following operands. Thisdefine is included in source member BIMFTRJ3:

CEDA Define File : BIMFTRF Group : FTRVSAM PARAMETERS DSNAme : BIMPCTFR.CONTROL.FILE LSrpoolid : None STRings : 003INITIAL STATUS STAtus : Enabled Opentime : Firstref DIsposition : ShareDATA FORMAT RECORDFormat : VOPERATIONS Add : Yes BRowse : Yes DELete : Yes REAd : Yes Update : Yes



If you will be using the Host Activity Log of BIM-PC/TRANFSER, add thefollowing FCT entry. This is provided in source member BIMFTRS1:

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)

If you are using RDO to define the log file, use the following operands. Thisdefine is included in source member BIMFTRJ3:

CEDA Define File : BIMFTRL Group : FTRVSAM PARAMETERS DSNAme : BIMPCTFR.LOG.FILE LSrpoolid : None STRings : 003INITIAL STATUS STAtus : Enabled Opentime : Firstref DIsposition : ShareDATA FORMAT RECORDFormat : FOPERATIONS Add : Yes BRowse : Yes DELete : Yes REAd : Yes Update : Yes

BIM-PC/TRANSFER contains a feature that allows VSAM datasets to betransferred to and from PC’s by specifying their cluster name. This featurerequires one or more ‘generic’ FCT entries that BIM-PC/TRANSFER willtemporarily use during the actual transfers. Refer to section “Cluster NameTransfer Feature” on page 205 to determine if you will need these FCT entries.Sample FCT entries for this feature are included in source member BIMFTRS1and RDO DEFINEs are contained in BIMFTRJ3.

MVS 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) -

Refer to the BIM-TMAN documentation for details of these operands.



Unlike CICS, BIM-TMAN does not require programs to be predefined to it suchas CICS PPT entries. You can ignore any reference in this manual to programdefinitions if you are only using BIM-TMAN.

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 MAINTTXN CODES” on page 192 for more information.

Except for the FILE operands for BIMFTRF and BIMFTRL shown above, you willonly need to provide additional FILE operands for the following types of VSAMdatasets:

1) Datasets defined in VSAM profiles that you need to upload into. You do notneed FILE operands for datasets transferred using the “Cluster NameTransfer Feature” described on page 205.

2) 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 DD name of the VSAM datasetaccess dataset access type

I = input only (default)U = updateL = load mode

strno VSAM number of strings (default is 3)type VSAM cluster type

KS = Keyed SequenceES = Entry SequenceRR = Relative Record

BIM-TMAN also requires that DDs be present for all VSAM datasets to beaccessed, and that all programs be available in LIBDEF search chains.

MVS Installation Step 8 - Customization

“MVS Installation Step 4 - Define the Host Control File” created severalCATEGORY definitions for your initial use. These default definitions will allowmost installations to begin using BIM-PC/TRANSFER immediately. To reviewthese definitions, bring up the CICS or BIM-TMAN system containing the abovedefinitions, and use the FTRM transaction. CATEGORY definitions are used todefine which transfers are allowed using BIM-PC/TRANSFER. Refer to thesection “Host Customization using the FTRM Transaction” on page 186 for moreinformation.



MVS Installation Step 9 - PC Program Installation

Install the PC program on the PCs that will be transferring data. You may haveseveral diskettes depending on which versions of the PC software you haveordered.

The section “Connecting the PC to the Host” on page 41 contains information foractivating the LU2 and/or APPC connections between the PC and the host.

MVS Installation Step 9a - Microsoft Windows 95/98 or NT 4.x

Insert the installation diskette containing the Windows 95/98/NT version ofBIM-PC/TRANSFER in a drive on your PC. Click the “Start” button, and selectthe “Run” entry. Enter the following command in the RUN dialog box:

A:SETUP.EXE


MVS Installation Step 9b - Microsoft Windows 3.1, 3.11, and NT 3.5.1

Insert the installation diskette containing the Windows or Windows NT versionof BIM-PC/TRANSFER in a drive on your PC. Select “Run” from the ProgramManagers “File” menu and enter the following command in the RUN dialog box:

A:SETUP.EXE


MVS Installation Step 9c - PC Program for OS/2

Insert the installation diskette containing the OS/2 version of BIM-PC/TRANSFER in a drive on your PC and enter the following at an OS/2command line:

A:INSTALL

-or-

A:INSTALL /T:path

where A: is the diskette drive containing the BIM-PC/TRANSFER PC installationdiskette, and “path” is the drive and directory into which you want BIM-PC/TRANSFER installed. The default path is “C:\BIMFTR”.



MVS Installation Step 9d - PC Program for DOS

Please review the “BIM-PC/TRANSFER Copyright Notice” on the back side ofthe cover page of this manual before installing the DOS version.

Insert the BIM-PC/TRANSFER PC diskette containing the DOS version into adrive, and enter the following commands:

MD bimftrCD bimftrA:INSTALL A:

where A: is the diskette drive containing the BIM-PC/TRANSFER PC installationdiskette, and 'bimftr' is the directory you want to install the software into.

MVS Installation Step 9e - PC Program README File

The PC diskettes contain a README file with information not available whenthis manual was printed. This file contains technical information about using andinstalling the PC software with various 3270 and APPC emulators.


Connecting the PC to the Host Page 41

Connecting the PC to the HostBIM-PC/TRANSFER can be used with a wide selection of PC to host connectionsand emulators. This section describes special rules and considerations requiredfor some emulators and connection types.

This section is organized by the following topics:

Topic Page

BIM-PC/TRANSFER Connection Settings............................................ 42

Single Connection Definition.................................................... 42

Connection Profile Definitions ................................................. 43

Profile List Dialog...................................................................... 44

Profile Details Dialog ................................................................ 45

Using Connection Profiles In Manual Transfers ..................... 46

Using Connection Profiles In Automatic Transfers................. 46

LU2 Settings............................................................................... 47

TCP/IP Settings......................................................................... 49

APPC Settings............................................................................ 50

LU2/3270 Connections Using Microsoft Windows.............................. 52

LU2/3270 Connections Using OS/2...................................................... 54

LU2/3270 Connections Using DOS. ...................................................... 55

TCP/IP Connections to the Host ........................................................... 57

APPC Connections Using Microsoft Windows or OS/2. ..................... 58

VTAM Definitions on the Host for APPC ............................................. 59

CICS Definitions on the Host for APPC ................................................ 60

BIM-PC/TRANSFER Definitions for APPC ......................................... 61

APPC Interface Configuration on the PC.............................................. 61


Page 42 Connecting the PC to the Host

BIM-PC/TRANSFER Connection Settings

All of the host connection settings used by BIM-PC/TRANSFER are contained inone of the following dialog screens.

The manual transfer program (BIMFTRx) and the automatic transfer program(BIMAFTx) each maintain their own connection settings. If you will be using bothprograms, you will need to define connection settings to each of them.

Depending on which PC environment you are using, you can either maintain asingle connection definition to the host, or you can maintain multiple"Connection Profiles" to one or more host systems. If you see a "Connection" tabon the "Settings" dialog, then refer to section "General Settings Dialog" on page 92for information on how to activate "Connection Profiles".

Single Connection Definition

Connection General Auto Log

BIM-PC/TRANSFER Settings

Apply Cancel

Advanced

Help Next

LU2 (3270 Emulation)

Connect: Session=A (BIMPCSHL.DLL)

LU6.2(APPC)

TCP/IP

Host Connection

This dialog is displayed by selecting the “Settings” button of the “Sign On”dialog, or by selecting “Settings” from the “File” Menu item of the main transferwindow. The "Connection" tab is used to define a single connection to a hostsystem.

Host Connection This box contains the selection for the type of hostconnection to be made, LU2/3270, TCP/IP or APPC.

Advanced Click this button to view/change the options in effectfor the selected Host Connection type.



Connection Profile Definitions

Profile General Auto Log


Apply Cancel

DEFAULT - TCP/IP - Default Connection

Profile List

Help Next

Active Profile:

This dialog is displayed by selecting the “Settings” button of the “Sign On”dialog, or by selecting “Settings” from the “File” Menu item of the main transferwindow. The "Profile" tab is used to define and maintain multiple connections toone or more host systems. Note that only one connection can be active at a time.

Active Profile This button shows the currently active ConnectionProfile. If you press this button, the "Profile DetailsDialog" will be displayed.

Profile List Click this button to change, add, or deleteConnection Profiles.



Profile List Dialog

Profile List

OK

DeleteChangeNewMake Current

DEFAULT - TCP/IP - Default Connection to ProductionTESTCICS - APPC - APPC Access to Test

This dialog is displayed by selecting the “Profile List” button of the “Profile”dialog. This dialog shows all of the "Connection Profiles" you have currentlydefined for the PC. The currently active profile is highlighted.

Make Current This button is used to set the currently selectedprofile as active.

New Click this button to define a new profile.

Change Click this button to change the currently selectedprofile.

Delete Click this button to delete the currently selectedprofile.

If either "New" or "Change" are pressed, the "Profile Details" dialog will bedisplayed.



Profile Details Dialog

DEFAULT - TCP/IP - Default Connection to Production

OK Cancel Help

LU2 (3270 Emulation)

LU6.2(APPC)

TCP/IP

Host Connection

Advanced

Description: Default Connection to Production

Name: DEFAULT

This dialog is used to display or alter a specific "Connection Profile". It isdisplayed as a result of one of the following:

1) Pressing the "Active Profile" button on the "Profile Settings" dialog.

2) Pressing either the "New" or "Change" buttons on the "Profile List" dialog.

Name This is a unique name you assign to each profile. Itcan be up to 8 characters in length. You assign thisname when the profile is first defined. It cannot bechanged.

Description This is a free-form description you can use to betteridentify each profile. Some non-blank value isrequired.

Host Connection This box contains the selection for the type of hostconnection to be made, LU2/3270, TCP/IP or APPC.

Advanced Click this button to view/change the options in effectfor the selected Host Connection type.



Using Connection Profiles In Manual Transfers

Once signed on to the Host, it is possible to change the "Connection Profile" fromwithin the Manual Transfer program. However, it is important to note that a signon does not occur when you change profiles. Consequently, if differentCICS/BIM-TMAN systems have differing sign on responses - for instance,allowing some access in CICS 1 and not allowing that access in CICS 2 - problemsare likely to occur. It is recommended that you do not change profiles in themiddle of the stream. Instead, you should exit the Manual Transfer program andrestart it. Press the "Settings" button on the "Sign On" dialog, and change theactive profile there.

Using Connection Profiles In Automatic Transfers

You can freely switch between different "Connection Profiles" from within theAutomatic Transfer Program with one provision, Each individual AutomaticTransfer Script, whether loaded from the PC or initiated from the Host, isrestricted to a single profile.

You can start the Automatic Transfer program using one profile and receive ascript from the host using a different profile. The PC will correctly switch backand forth between profiles as required. Likewise, using the LOADNEXT= facilityof the #OPTION statement, you can string together several Automatic TransferScripts, each using a different "Connection Profile". You can even use the newprompting facility to dynamically select which profile to use.

The "Connection Profile" is identified on the #OPTION statement of theAutomatic Transfer Script as:

#OPTION PROFILE=name



LU2 Settings

This dialog is displayed if the “Advanced” button is clicked when the LU2 HostConnection is active:

BIM PC/TRANSFER LU2 Settings

Time Out Wait (in secs.)

Input Inhibit Flicker

3270 Emulator

CICS Transaction Id

DLL Name

Parameters

Struct. Fields

Upload Buffer Size

Download Buffer Size

Logon Script

Logon Attempts

Logoff Script

BIMACS3.DLL

FTRT,

ANY

A

NORESET

Session

Ok Cancel Help

Browse

45

16000

8000

1

1

LOGON.SMP

BrowseLOGOFF.SMP

Converse

Session Specify the short name, usually A through E, of 3270emulator session that BIM-PC/TRANSFER is to use tocommunicate to the host.

Note that this field is “case” sensitive. Most emulatorpackages will expect this field to be specified in uppercase. Check with your emulator documentation todetermine its requirements.

NS/Elite Plus™ expects this field to be in lower case.

Time Out Wait Only change this field when advised by BIM.

Input Inhibit Flicker Only change this field when advised by BIM.

3270 Emulator Only change this field when advised by BIM or later inthis section for specific emulator packages.

CICS Transaction id This value must be the same as the value specified in



“VSE Installation Step 6 - CICS/VS Table Additions”on page 23 or “MVS Installation Step 6 - CICS/VSTable Additions” on page 34.

DLL Name This value is only used for Microsoft Windowsemulators. The section “DLL Specification” on page 52contains a table of the DLLs provided with BIM-PC/TRANSFER.

Parameters Only change this field when advised by BIM.

Struct. Fields This field is used to specify whether the LU2connection should use the structured fields format. Atthe time this manual is being written, the onlyemulators known to support structured fields areIBM’s PC/3270 and Communications Manager/2.Structured fields will increase the transfer speed by 5 to10 times over standard LU2 connections.

This field can be set to one of the following:

No Structured fields are not to be used.Full Use Structured fields.Converse Use a slower version of structured fields. If

you experience problems with the “Full”option, such as sequence errors during thetransfer, then try this option.

Upload Buffer Size Only change this field when advised by BIM.

Download Buffer Size Only change this field when advised by BIM.

Logon Script This field is used to provide the name of an optionallogon script to be used by BIM-PC/TRANSFER to logonto the host CICS or BIM-TMAN system. The“Browse” button can be used to display a standard filedialog box to aid in the location of your logon script.Refer to section “Logon/Logoff Scripts” on page 69 formore information.

Logon Attempts This field is used to specify the number of times thelogon script will be executed before giving up. Eachtime the end of a logon script is reached withoutexecuting a #BYE command, BIM-PC/TRANSFER willwait for one minute, and then retry the script. Thisprocess will continue until this limit is reached.

Logoff Script This field is used to provide the name of an optionallogoff script to be used by BIM-PC/TRANSFER to logoff the host CICS or BIM-TMAN system. The “Browse”button can be used to display a standard file dialog boxto aid in the location of your logoff script. Refer tosection “Logon/Logoff Scripts” on page 69 for moreinformation.



TCP/IP Settings

This dialog is displayed if the “Advanced” button is clicked when the TCP/IPHost Connection is active:

Ok

BIM PC/TRANSFER TCP/IP Settings

Cancel Help

Server Name/Address

Port Number

Maximum TCP/IP Buffer

Host Transfer Net Name

172.17.2.30

4097

1000

YOURPC

Server Name/Address Specify the TCP/IP address of the host you wish toestablish a connection with. This value can either bean IP address as shown above, or the name of a hostfrom the HOSTS file on your PC.

Port Number Specify the port number assigned to the hostcomponent of BIM-PC/TRANSFER for its’ TCP/IPinterface. This must be the same value specified insection “TCP/IP Connection Options” on page 250.

Maximum TCP/IP Buffer Only change this field when advised by BIM.

Host Transfer Net Name This field is used to identify your PC to the host. It isused by the HOSTAFT feature as your PCs“Netname”.



APPC Settings

This dialog is displayed if the “Advanced” button is clicked when the APPC HostConnection is active:

Ok

BIM PC/TRANSFER APPC Settings

Cancel Help

Local TP Name

Local LU Alias

Partner LU Alias

CICS Transaction ID

Mode Name

APPC Trace

Buffer Size

APPC Emulator

Upload Pacing

BIMAPPCX

PCLU

BIMCICST

APPC

None

FTRT

8116

IRMA

4

Local TP Name This is the name of the APPC DLL used by BIM-PC/TRANSFER. There currently is only one supplied.It is named BIMAPPCX.DLL.

Local LU Alias This is the LU name of the PC as defined to VTAM.

Partner LU Alias This is the VTAM APPLID of the CICS system thatcontains the host side of BIM-PC/TRANSFER.

CICS Transaction id This value must be the same as the value specified in“VSE Installation Step 6 - CICS/VS Table Additions”on page 23 or “MVS Installation Step 6 - CICS/VSTable Additions” on page 34.

Mode Name This must match the logmode defined to the PC,VTAM, and CICS for the APPC connection.

APPC Trace Only change this field when advised by BIM.



Buffer Size Maximum data block transmitted to the host. Onlychange this value when advised by BIM or specificvendor instructions contained in this manual.

APPC Emulator This list box can be set to IRMA or NETSOFT. If youare not using NETSOFT use the default of IRMA. BIM-PC/TRANSFER needs to know if you have theNETSOFT APPC emulator.

Upload Pacing This field controls the number of APPC buffers thatwill be sent to the host before requiring a confirmation.The default is 4. If you specify to high a number,VTAM may experience buffer problems, and the PCmay lock up. Download pacing is controlled by theVTAM VPACING operand on the LU definition.

The remainder of this section describes further considerations for the variousconnection types.



LU2/3270 Connections Using Microsoft Windows.

This section describes the special installation and customization requirements forusing a Windows 3270 emulator with BIM-PC/TRANFSER.

HLLAPI Application Interface

BIM-PC/TRANSFER communicates to the 3270 emulators using an applicationinterface known as the HLLAPI or the EHLLAPI. Each emulator has its ownmethod of installing this interface. If when you attempt to use BIM-PC/TRANSFER, you get a windows message about a DLL not found, then thisinterface has probably not been installed for your emulator.

PATH Statement

The PC directory containing your 3270 emulator, for example: C:\EXTRAWINfor Attachmate Extra!, must be included in the PATH statement contained inyour AUTOEXEC.BAT file. You will need to re-boot your PC after making thischange. If you are unable to add the directory to your PATH statement due to the128 byte limitation, then the only other alternative is to run BIM-PC/TRANSFERfrom within your emulators directory. Note: this requirement does not apply toIBM PC/3270.

DLL SpecificationBIM-PC/TRANSFER is delivered with several DLL modules that are used tocommunicate with the supported Windows emulator packages. The followingtables contain the names of the DLLs used for each emulator. The default DLL isindicated by an (*) in each table. For the other DLL's, change the “DLL Name”field of the “LU2 Settings” dialog described on page 47.

Windows 3.1 version of BIM-PC/TRANSFER

IRMA BIMACS3.DLL (*)

IRMA 3.x.x BIMNSFT.DLL

EXTRA in Windows 3.1 BIMACS3.DLL

16-Bit EXTRA in Windows 95/NT BIMNSFT.DLL

EXTRA 5.x BIMNSFT.DLL

NS/3270 BIMNSFT.DLL

TLINKW BIMNSFT.DLL

RUMBA BIMRMBA.DLL

PC/3270 BIMPCSHL.DLL

FORVUS BIMPCSHL.DLL

Passport BIMPCSHL.DLL

1472/PC (Memorex) BIMPCSHL.DLL

DynaComm/Elite BIMDYN.DLL

Novell 3270 BIMNVL.DLL



Windows 95/98/NT version of BIM-PC/TRANSFER

Attachmate Personal Client BIM32WHL.DLL (*)

Attachmate version 6.2 and above BIM32E62.DLL

Reflection For IBM BIM32E62.DLL

NS/Elite Plus BIM32HLL.DLL

PC/3270 (IBM) BIM32PCS.DLL

Rumba 95/NT for Mainframe BIM32HLL.DLL

Verify Session ID

The HLLAPI interface requires that BIM-PC/TRANSFER communicates via aspecific 3270 session. The default session ID used by BIM-PC/TRANSFER is “A”.Your emulator should display the session ID either as part of the session title baror on the bottom line of the session. If you see a value other than “A”, you mustchange the “Session” field of the “LU2 Settings” dialog described on page 47.

BIM-PC/TRANSFER Configurator

BIM-PC/TRANSFER contains an automatic configuration program for the PC. Itcan be found in the ”BIM PC TRANSFER Program Group” as “Configurator”.This program has dialogs containing important setup information for each of thesupported emulators.



LU2/3270 Connections Using OS/2.

This section describes the special installation and customization requirements forusing a native OS/2 3270 emulator, such as Communications Manager/2 withBIM-PC/TRANFSER.

HLLAPI Application Interface

BIM-PC/TRANSFER communicates to the 3270 emulators using an applicationinterface known as the HLLAPI or the EHLLAPI. Each emulator has its ownmethod of installing this interface. If when you attempt to use BIM-PC/TRANSFER, you get a windows message about a DLL not found, then thisinterface has probably not been installed for your emulator.

Verify Session ID

The HLLAPI interface requires that BIM-PC/TRANSFER communicates via aspecific 3270 session. The default session ID used by BIM-PC/TRANSFER is “A”.Your emulator should display the session ID either as part of the session title baror on the bottom line of the session. If you see a value other than “A”, you mustchange the “Session” field of the “LU2 Settings” dialog described on page 47.



LU2/3270 Connections Using DOS.

This section describes the special installation and customization requirements forusing a DOS 3270 emulator with BIM-PC/TRANFSER.

BIMDOSCK Program

Typically, any problems with these emulator environments will cause your PC tolock up, requiring it to be re-booted.

A special program “BIMDOSCK.EXE” has been provided on the installationdiskette. You should run this program to diagnose the problem.

Program BIMDOSCK will display a series of messages as it attempts to use eachfunction of the HLLAPI. If a failure occurs, the message indicates where thefailure occurred.

A list of the available session IDs will be displayed, and you will be prompted toenter one of them. This will be followed by several other messages as it completesits testing.

If you entered a session ID other and “A”, and this allowed BIMDOSCK tocomplete normally, then change the “Session” field of the “LU2 Settings” dialogdescribed on page 47.

If BIMDOSCK does not complete correctly, you should get one of the followingmessages:

HLLAPI not installed (vector = NULL)

This indicates that the HLLAPI interface has not been installed for yourDOS emulator. You should consult the PC documentation for youremulator to determine the proper installation procedure.

Attempting Reset System (21)

Your PC may lockup here. If so, the HLLAPI interface is not installedproperly. You should consult the PC documentation for your emulator todetermine the proper installation procedure.

RC=1 - Session not connected or invalid presentation space ID

This message normally appears after you key in the Session ID. Try againwith another allowable session ID. If that does not work, then check withthe emulation software vendor.

Note: If you are running on a Novell Network, you should use “0” (zero)for the session ID. (See also the Novell note below.)



RC=5 - keyboard is locked (inhibited)

Check the status of the 3270 session. For some reason it has gone intoinput inhibit. Reset and clear the 3270 session and retry the test.

RC=9 - System Error

This indicates an error condition within the 3270 emulator. Check withthe emulation software vendor for any known problems.

IRMA(DCA) E78+ Special Processing

If you are using this emulator, you must load the HLLAPI interface beforeloading the 3270 emulation software.

TLINK Special Processing

This emulator only supports 3270 model 2 sessions via the HLLAPI interface.You must, therefore, ensure that the host session being used for the transfer is amodel 2. You must also execute BIMFTRD and BIMAFTD with the followingoption:

BIMFTRD /M2BIMAFTD /M2

The /M2 option ensures that BIM-PC/TRANSFER uses a model 2 buffer size.TLINK does not properly report the buffer size to applications using theHLLAPI.



TCP/IP Connections to the Host

This section describes the special installation and customization requirements forusing a TCP/IP connection between a PC and the host. TCP/IP is currently onlysupported in VSE.

Overview

The following actions must be performed before TCP/IP connections can beused:

1) You must have TCP/IP for VSE from Connectivity Systems installed andoperational on your host system. It is very important that the TCP/IPpartition be at a higher VSE priority than the partition that BIM-PC/TRANSFER is running in (BIM-TMAN or CICS).

2) The transactions FTRI and FTRP and programs BIMFTRIP and BIMFTRI2must be defined to CICS or BIM-TMAN. Refer to “VSE Installation Step 6 -CICS/VS Table Additions” on page 23.

3) The TCP/IP host interface options must be defined. Refer to “TCP/IPConnection Options” on page 250.

4) The BIM-PC/TRANSFER ‘Listen’ task for TCP/IP must be activated. Seebelow.

5) The TCP/IP interface options must be defined on the PC. Refer to “TCP/IPSettings” on page 49.

Activating the ‘Listen’ Task

The TCP/IP interface of BIM-PC/TRANSFER requires that a ‘Listen’ task beactive in the BIM-TMAN or CICS system in which the host side of BIM-PC/TRANSFER is executing.

This ‘Listen’ task maintains a SOCKET ‘Open’ request with the TCP/IP partition,waiting for a PC to make a connection. If the ‘Listen’ task is not active, no TCP/IPconnections can be established.

Automatic Activation

The ‘Listen’ task can be automatically activated at CICS or BIM-TMAN startup.To do this, refer to “VSE Installation Step 9 - Activating the TCP/IP Interface” onpage 26.

Manual Activation / Deactivation

The ‘Listen’ task can be manually activated and/or deactivated by enteringtransaction ‘FTRP’ at a BIM-TMAN or CICS terminal and responding to thedisplayed message.



APPC Connections Using Microsoft Windows or OS/2.

This section describes the special installation and customization requirements forusing an APPC Interface with BIM-PC/TRANFSER.

APPC Connection Overview

An APPC connection between BIM-PC/TRANSFER and the host requires a seriesof specific definitions in the following places:

1) VTAM definitions on the host

• You will need to know the network ID of you host. This is contained inthe NETID= startup option of VTAM.

• You will need to know the VTAM APPLID of the CICS systemcontaining the host side of BIM-PC/TRANSFER.

• You will need a LU definition for each PC session. The LU name andLOCADDR of these definitions will be required in various otherdefinitions described below.

• You will need a LOGMODE definition for the APPC session.

2) You will need to define a Connection and Session to CICS for each PC. This isdone used RDO (CEDA).

3) You will need to configure the APPC interface software on the PC.

4) You will need to customize the BIM-PC/TRANSFER Connection Settingsbased on the above definitions.

Each of these steps are described below in detail.



VTAM Definitions on the Host for APPC

There are four types of definitions required for VTAM. These may be alreadydefined on your system, however, you will need to know the contents of thesedefinitions because they are used by the other APPC definitions required for theconnection.

Network ID This value is contained in the NETID= operand of yourVTAM startup commands. In the examples in thissection, we use USBIM01.

CICS APPLID This value is the name field of the VTAM APPLstatement for the CICS or BIM-TMAN that contains thehost side of BIM-PC/TRANSFER. In the examples inthis section, we use BIMCICST.

Make sure that your CICS or BIM-TMAN APPLstatement includes the following operand:

PARSESS=YES

If you are using BIM-TMAN on the host, make sure theAPPL statement for BIM-TMAN includes the followingoperands:

APPC=YES,DLOGMOD=APPC,

PC LU Definitions You will need to define an LU for each PC using anAPPC connection. You may already have one or moreLUs defined for 3270 sessions. You will need to add anew one for APPC:

PCLU LU LOCADDR=6,DLOGMOD=APPC

PCLU is the LU name. You can choose any valueyou want. It will be used in several otherdefinitions below.

LOCADDR can also be any value you want, but it is alsoused in several definitions below.

APPC Logmode The APPC connection with VTAM requires a specificlogmode to be defined in the CICS and/or BIM-TMANMODETAB. The following definition can be used:

1........10.....16 72APPC MODEENT LOGMODE=APPC, X FMPROF=X'13',TSPROF=X'07', X PRIPROT=X'B0',SECPROT=X'B0', X COMPROT=X'D0B1', X RUSIZES=X'8989',ENCR=B'0000', X PSERVIC=X'060200000000000000000300'



CICS Definitions on the Host for APPC

You will need to define a CICS SESSION and CONNECTION for each PC usingan APPC connection.

CEDA DEFINE GROUP(FTR) CONNECTION(PC01) (NOTE 1) NETNAME(PCLU) (NOTE 2) ACCESSMETHOD(VTAM) (REQUIRED) PROTOCOL(APPC) (REQUIRED) SINGLESESS(YES) (REQUIRED) DATASTREAM(USER) (REQUIRED)

CEDA DEFINE GROUP(FTR) SESSIONS(PC01SESS) CONNECTION(PC01) (NOTE 1) MODENAME(APPC) (NOTE 3) PROTOCOL(APPC) (REQUIRED) MAXIMUM(1,1) (REQUIRED) SENDSIZE(4096) RECEIVESIZE(4096) TRANSACTION(FTRT) (NOTE 4) AUTOCONNECT(YES)

NOTES:

1) CONNECTION name PC01 can be any value you desire, but must be uniquefor each PC, and must be the same for the SESSIONS and CONNECTIONdefinitions.

2) PCLU must be the LU name defined to VTAM for each PC session.

3) APPC must be the name of the LOGMODE defined to VTAM for APPCsessions. It must be contained in the MODETAB= specified on the VTAMAPPL statement for the CICS system.

4) FTRT must be the CICS transaction id defined in installation step 5.

5) If you define a new group for these CEDA definitions, remember to add thenew group to your existing CICS startup list and using the CEDA installfunction to activate the new definitions:

CEDA ADD GROUP(FTR) LIST(yourlist)CEDA INSTALL GROUP(FTR)

CICS System Initialization Table (SIT)

APPC connections with CICS require the following SIT operand:

ISC=YES,



BIM-PC/TRANSFER Definitions for APPC

Refer to the section “BIM-PC/TRANSFER Connection Settings” on page 42 for adescription of the APPC connection settings.

Local LU Alias This is the LU name of the PC as defined to VTAM.In our example it is “PCLU”.

Partner LU Alias This is the VTAM APPLID of the CICS system thatcontains the host side of BIM-PC/TRANSFER. In ourexample it is “BIMCICST”.

CICS Transaction ID This value must be the same as the value specified in“VSE Installation Step 6 - CICS/VS Table Additions”on page 23 or “MVS Installation Step 6 - CICS/VSTable Additions” on page 34. In our example it is“FTRT”.

Mode Name This must match the logmode defined to the PC,VTAM, and CICS for the APPC connection. In ourexample it is “APPC”.

PATH Statement for Windows version

The PC directory containing your APPC emulator, for example: C:\IRMAWINfor Irma Workstation for Windows, must be included in the PATH statementcontained in your AUTOEXEC.BAT file. You will need to re-boot your PC aftermaking this change. If you are unable to add the directory to your PATHstatement due to the 128 byte limitation, then the only other alternative is to runBIM-PC/TRANSFER from within your emulators directory.

APPC Interface Configuration on the PC

This configuration process will vary depending on the APPC interface vendoryou are using, and the type of physical connection between the PC and the host,(Token-Ring, SDLC, etc.).

We have included the basic configuration requirements for several vendors. Ifyour vendor is not described here, you should be able to extract the requiredparameters from those described here.

We have not included the definitions on the PC required for the physicalconnection to the host. Refer to your vendors documentation for assistance inthese definitions.



IRMA Workstation for Windows (APPC)

You will need to define three types of definitions:

• Local LU Definition• Mode Definition• Remote LU Definition

Local LU Definition: LU Name: PCLUFull Network Name: USBIM01.PCLU

Session Limit: 1 (required)LU Number: 6

Mode Definition: Name: APPCSession Limit: 1 (required)

Max RU size for send: 4096Max RU size for recv: 4096

Remote LU Definition: LU Name: BIMCICSTFull Network Name: USBIM01.BIMCICST

Uninterpreted LU Name: BIMCICST

Where:

PCLU must match the VTAM LU definition for the PC.6 must match the VTAM LU definition for the PC.USBIM01 must match the VTAM NETID for your system.APPC must match the VTAM LOGMODE for APPC sessions.BIMCICST must match your CICS APPLID for BIM-PC/TRANSFER.



RUMBA (APPC)

RUMBA release 3.2 requires that the “Buffer Size” field of the BIM-PC/TRANSFER Interface Dialog be set to 2029. If any larger value is used, yourPC will lock up. This problem has been reported to RUMBA and may becorrected in a future release.

You must run CONFIG.EXE which is found in the \RUMBA directory. There arefour types of definitions that need to be setup:

• Connection Definition• Local LU Definition• Mode Definition• Remote LU Definition

Use the “Add” button to create new entries:

Connections:Select the connection you will be using:

Block Id: 001Destination Address: Token ring address of Ctl

unit

Local LU Definition: LU Alias: PCLULU Name: PCLU

[Push the “advanced” button]LU Address: 6

Check the “Use As Default LU” box

Mode Definition: Name: APPC(remaining defaults areOK)

Remote LU Definition: LU Alias: BIMCICSTLU Name: BIMCICST

Connection: match the connection above[Push the “advanced” button]

Network Name: USBIM01Uninterpreted LU Name: BIMCICST

Check the “Use As Default LU” box

Where:




DynaComm/Elite (APPC)

DynaComm/Elite is jointly produced by NetSoft and FutureSoft. DynaComm,FutureSoft are registered trademarks of Future Soft Engineering, Inc.

There are four types of profiles that need to be setup:

• Initial Session Limit Profile• Local LU Profile• Transmission Service Mode Profile• Partner LU Profile

Initial Session Limit Profile:Profile Name: BASE

Local LU Profile: LU Alias: PCLULU Name: PCLU

LU Address: 06

Mode Profile: Profile Name: APPCMaximum RU Size: 4096

Partner LU Profile: Partner LU Alias: BIMCICSTLocal LU Alias: PCLU

Partner LU Network Name: USBIM01Partner LU Name: BIMCICST

Partner LU Uninterpreted Name: BIMCICSTMode Table Entries: (link APPC and BASE

together)

Where:


You must also specify 'NETSOFT' for the APPC Emulator in the “APPC Settings”Dialog described at the beginning of this section.



Communications Manager/2 for OS/2 (APPC)

You will need to define the following types of definitions:

• Data Link Control (DLC). This definition will vary depending on the type ofphysical connection between the PC and the host.

• SNA Local Node Characteristics• SNA Connection• SNA Features

Launch the Communications Manager Setup program, and select the “APPCAPI’s” option from the “Configuration Definition” dialog. Then follow thedialogs to add the following definitions:

SNA Local Node Characteristics:Network ID: USBIM01

Local Node Name: PCPUNode Type: End node

SNA Connections:Partner Type: To Host

Link Name: LINK001(depends on yourconnection to the host)

SNA Features:

Local LU: LU Name: PCLUAlias: PCLU

Dependent LU NAU: 6Host Link: LINK001

Partner LU: Fully Qualified LU Name: USBIM01.BIMCICSTAlias: BIMCICST

Partner LU is Dependent: (check this box)Uninterpreted Name: BIMCICST

Mode Definition: Name: APPCClass of Service: #CONNECT

Mode Session Limit: 1 (required)Compression: (Prohibited)

Maximum RU Size: 4096

Where:

PCPU must match the VTAM PU definition for the PC.PCLU must match the VTAM LU definition for the PC.6 must match the VTAM LU definition for the PC.USBIM01 must match the VTAM NETID for your system.APPC must match the VTAM LOGMODE for APPC sessions.BIMCICST must match your CICS APPLID for BIM-PC/TRANSFER.



IBM Personal Communications PC/3270 (APPC)

Start the “SNA Node Configuration” program and follow the dialogs to add thefollowing entries:

Configure Node:Fully Qualified CP name: USBIM01.PCPU

CP alias: PCPULocal Node ID: (if needed)

Configure Devices:

This definition will vary depending on the type of physical connectionbetween the PC and the host.

Configure Connections:

This definition will vary depending on the type of physical connectionbetween the PC and the host.

(Advanced) Auto activate support: (check this box)(Advanced) PU name: PCPU

Configure Partner LU 6.2:Partner LU name: USBIM01.BIMCICSTPartner LU alias: BIMCICST

Fully Qualified CP name: USBIM01.BIMCICST(Advanced) Conversation security support: (remove check mark)

(Advanced) Parallel session support: (remove check mark)

Configure Modes:Mode name: APPC

PLU mode session limit: 1 (required)(Advanced) Class of Service name: #BATCH

(Advanced) Maximum RU size: 4096

Configure Local LU 6.2:Local LU name: PCLUDependant LU: (check this box)Local LU alias: PCLU

PU name: PCPUNAU address: 6

Where:




Attachmate Personal Client (APPC)

Start the “APPN Configuration” program, load the DEFAULT.XCP file, andfollow the dialogs to add the following entries:

Node Definition:Network ID: USBIM01

CP name: PCPUCP alias: PCPU

Default Node ID and PU ID: (if needed)Maximum Locates: 8

Locate Timeout: 300

Data Link Control:

This definition will vary depending on the type of physical DLC typeconnection between the PC and the host.

Negotiable links: (check this box)Activate at startup: (check this box)

Port:

This definition will vary depending on the type of physical connectionbetween the PC and the host. Generally the default settings will suffice.

Link:Activate at startup: (check this box)

Host Connection: (check this box)Block ID and PU ID must be the same as in the Node Definition.

Modes:Mode name: APPC

PLU mode session limit: 1Maximum: 1

Min contention winner: 1Class of Service name: #BATCH

Maximum RU size: 4096

Local LU 6.2:Local LU name: PCLULocal LU alias: PCLU

PU name: PCPUNAU address: 6

Session limit: 1

Partner LU 6.2:Network ID: USBIM01

Partner LU name: BIMCICSTPartner LU alias: BIMCICST

PLU unqualified name: BIMCICST



Conversation security support: (remove check mark)Parallel session support: (remove check mark)

Maximum logical record size: 32765

Where:



Logon/Logoff Scripts Page 69

Logon/Logoff ScriptsIf you are using an LU2/3270 connection to the host for BIM-PC/TRANSFER, asession must first be established with either CICS or BIM-TMAN such that thePC can issue host transactions (FTRT) in the session. This will normally requireentering VTAM LOGON commands, and possibly a CICS signon command. Youcan either perform these tasks manually, each time you start your 3270 emulator,or these tasks can be “recorded” in a “Logon Script” that BIM-PC/TRANSFERcan “execute” prior to each signon attempt.

Refer to field “Logon Script” on page 48 for information on how to activate aLogon Script.

A Logoff Script can also be created to terminate the LU2/3270 connection whenyou exit the PC program.

Refer to field “Logoff Script” on page 48 for information on how to activate aLogoff Script.

Logon and Logoff scripts can also be specified in Automatic Transfer Scripts viathe LOGON= and LOGOFF= operands of the #OPTION statement. See page 130for more information.

There are four commands that can be entered into a Logon/Logoff Script:#LOOK, #AT, #SEND and #BYE. These commands are described in detail below.

Logon/Logoff Scripts can either be created using a PC text editor, and saved as astandard ASCII text file, or they can be “recorded” using the provided logonscript recorder described below.

#LOOK

#LOOK row col data.to.look.for

#LOOK CLEARSCREEN

The #LOOK command describes data to be found at a specific location on the3270 screen. Commands following the #LOOK, up to the next #LOOK, will notbe executed unless the #LOOK has been satisfied.

Row and col define the position on the 3270 screen to be interrogated. Row andcol are relative to one making the upper left hand position of the screen row 1, col1.


Page 70 Logon/Logoff Scripts

The #LOOK CLEARSCREEN can only be specified in a Logoff Script. It will beignored in a Logon Script. It can also only appear once in the script. This #LOOKcan be used to respond to a clear (or empty) 3270 screen.

Example

#LOOK 23 7 APPLID:

This instructs BIM-PC/TRANSFER to look at row 23, column 7 of the 3270 screenfor the character string "APPLID:". If found, subsequent commands will beprocessed. If not found, BIM-PC/TRANSFER will skip forward to the next#LOOK or the end of the script whichever comes first.

#AT

#AT row col data.to.send.to.the.host

The #AT command supplies data that is to be entered into the 3270 screen at aspecific location. The #AT command will be processed if a preceding #LOOKwas satisfied. You can have as many #AT commands as needed to satisfy yourrequirements.

Row and col define the position on the 3270 screen to be interrogated. Row andcol are relative to one making the upper left hand position of the screen row 1, col1.

Example

#AT 23 15 LOGON APPLID(BIMWNDOW) LOGMODE(SNX32704)

At row 23, line 7, BIM-PC/TRANSFER will put the string "LOGONAPPLID(BIMWNDOW) LOGMODE(SNX32704)".

#SEND

#SEND keystroke

The #SEND command causes a 3270 attention key to be sent to the host. Anydata entered onto the 3270 screen by preceding #AT commands will also betransmitted according to the standard 3270 protocol.

Keystroke can be one of the following 28 supported 3270 attention keys:

ENTER PF4 PF11 PF18CLEAR PF5 PF12 PF19PA1 PF6 PF13 PF20



PA2 PF7 PF14 PF21PF1 PF8 PF15 PF22PF2 PF9 PF16 PF23PF3 PF10 PF17 PF24

Example

#SEND ENTER

Sends a 3270 enter key to the host.

#BYE

#BYE

The #BYE command signifies that the logon process is successfully completed.Script processing is not considered complete until a #BYE is encounteredfollowing a successful #LOOK.



Example Logon Script

The script below is the one used by BIM for testing purposes. As shown in thisexample, comment lines can be inserted into the script by specifying an ‘*’ incolumn 1 of each comment line.

** (1) VTAM Error Response*#LOOK 2 1 INVALID COMMAND SYNTAX#AT 3 1 BIMWNDOW#SEND ENTER** (2) VTAM Error Response*#LOOK 2 1 UNSUPPORTED FUNCTION#AT 3 1 BIMWNDOW#SEND ENTER** (3) VTAM MSG10 Screen*#LOOK 23 7 APPLID:#AT 23 15 BIMWNDOW#SEND ENTER** (4) BIMWNDOW Signon*#LOOK 22 9 USERID:#AT 22 17 DWD#AT 22 49 GARBONZO#SEND ENTER** (5) Open BIMWNDOW Session*#LOOK 2 16 APPL#AT 2 21 TEST#SEND ENTER#BYE** (6) VTAM MSG10 Screen (DFT)*#LOOK 13 27 APPLID:#AT 13 36 TEST#SEND ENTER#BYE

The first two entries in the sample script are intended to handle VTAM errorsthat may arise during Automatic Transfer processing. Your scripts shouldcontain similar entries. Automatic Transfer may attempt to initiate the filetransfer transaction, FTRT, when not properly logged on - for instance, CICScame down while Automatic Transfer was running. The steps that AutomaticTransfer takes to initiate a transaction will typically result in a blank screen and aVTAM error response. You need to cover for this eventuality in your logon script.



The third entry handles BIM's standard VTAM MSG10 screen. The first threeentries together will all attempt to start BIMWNDOW by keying it's VTAMAPPLID and sending an ENTER key to the host.

The fourth entry in the script deals with the signon panel returned byBIMWNDOW. Note that two #AT commands are used here, one to supply useridand one to supply password (no, it's not my "real" password).

The fifth entry in the script handles the BIMWNDOW session panel. Here wedirect ourselves to the test CICS system. This entry contains the #BYE commandindicating that at this point, the logon process is complete and BIM-PC/TRANSFER can now begin/resume its transfer activities.

The sixth and final entry in the script handles one of the subtleties of logons atBIM. PC access via our DFT connection returns a slightly different MSG10 screenthan access through the token ring. Here, we go directly to the test CICS systemwithout passing through BIMWNDOW. This entry also contains a #BYEindicating completed logon.

Example Logoff Script

The script below will logoff a CICS system, and return the 3270 session to VTAM.

#LOOK CLEARSCREEN#AT 1 1 CSSF LOGOFF#SEND ENTER#BYE

Example Automatic Transfer Scripts

Script 1#OPTION LOGON=cics.no.1 - LOGOFF=logoff.cics - LOADNEXT=script2...#END

Script 2#OPTION LOGON=cics.no.2 - LOGOFF=logoff.cics...#END

When you load and execute Script 1, at its completion, it will logoff and then loadScript 2 for processing. Scripts 1 and 2 can each communicate with different hostsystems. Any number of scripts can be chained together in this manner.



BIMLOGON - Logon/Logoff Script Recorder

You can create your logon/logoff script(s) manually but it can become tedious.To simplify things, we supply a program, BIMLOGON.EXE, for Windows andOS/2. (There is no script recorder provided for DOS.) With this program you canpoint and click your way through the logon process.

**** BIM VTAM LOGON APPLID OPTIONS **** BIMWNDOW - BIMWNDOW MULTIPLE SESSION M CICSPROD CICS PROD - PRODUCTION CIC CICSTEST TEST - TEST CICS/VSE BIMEDIT EDIT EDTR - VSE VTAM ACCES BIMEDITT - VSE TEST BIM-E P390TSO - P390 TSOENTER APPLID:

BBB BBBBB III III MMM MM BBB BBB IIIIII IIIIII MMM MM BBB BBB IIIIII IIIIII MMM MM BBB BBB III III MMM MM BBBBBBBBBBBBBBBB IIIIIIIIIIIIIIII MMMMMMMMM BBBBBBBBBBBBBBB IIIIIIIIIIIIIIII MMMMMMMMM

File Options

BIM-PC/TRANSFER - Logon Script Recorder

Select Data to LOOK for logon.smp

This is the main window for the Logon Script Recorder. The body of window willbe blank when you first start the program. In this example, we are showing theVTAM MSG10 screen here at BIM.

Option Pull Down

Session Parameters

Host Interface . . .

Option This menu results from selecting“Option” from the menu bar. You canselect this with the PC mouse, or bypressing the key combination ALT-O.

BIMLOGON takes its “Host Interface” options from the same source as theAutomatic Transfer Program, BIMAFT(x). If necessary you can change them forpurposes of creating a logon script. BIMAFT's options will not be affected if youdo.

The “Host Interface” dialog is an abbreviated version of that available withBIMAFT(x). It contains only those fields relevant to the logon process. Refer tosection “LU2 Settings” on page 47 for a description of this dialog.



File Pull Down

File

Exit

Try Script . . .

Mark #BYE

Record . . .

This menu results from selecting“File” from the menu bar. You canselect this with the PC mouse, or bypressing the key combination ALT-F.

The options are:

Record ... When you select this entry, the current contents of the 3270session will be displayed in BIMLOGON's main window.

Try Script ... Select this entry to test an existing Logon/Logoff Script. Youwill be prompted for the filename of the script to be tested.

Mark #BYE This entry will insert a #BYE command into the current script.

Exit This will exit the program.

Recording A Script

To begin recording a script, select File and choose "Record." You must also haveyour 3270 emulator session up and it should be displaying your VTAM MSG10screen.

When you select “Record”, the current contents of the 3270 session will bedisplayed in BIMLOGON's main window. 3270 attributes will be displayed assolid boxes in Windows, and little smiley-faces in OS/2. You can scroll thedisplay up and down and left and right by using the mouse on the scroll bars atright and bottom of the window.

Now you need to select the data that BIM-PC/TRANSFER uses to identify thisparticular 3270 screen (this is the data that will be placed into the #LOOKcommand described above). Position the mouse on the data and holding downthe left mouse button, drag the mouse through the data on the screen. Note: donot select attributes as part of this data.

When you release the left mouse button, you will be presented with one or moredialogs prompting you to enter data onto the screen.

Send Data to Host L:22,C:53

ENTER APPLID:

AID Key

Ok Cancel Skip

NONE



This dialog will appear once for every keyable position on the 3270 screen as longas the "AID key" field is left to "NONE". In the title bar, the line and columnposition are indicated. In order to assist you in determine what to key, dataimmediately to the left of this position on the 3270 screen is displayed in thedialog.

You can press the "Cancel" button at any time to terminate the script constructionprocess. Nothing will be saved and the contents of the 3270 screen will remainunchanged.

You can press the "Skip" button to skip this field on the 3270 screen. If you don'tneed to answer every possible entry field, simply skip the ones you don't needfor this logon.

When you have supplied all necessary data, on the last or only keyable field, youshould select "AID key" by pushing its little down arrow button. This willprovide you with a list of the 28 possible attention keys. Select the one you want(probably the ENTER key).

When an attention key is selected, BIMLOGON will quit prompting for inputdata and attempt the process the script fragment just defined. This can take a fewseconds to complete. When processing is complete, you will be asked:

BIMLOGON

Did your entries work as expected?

Yes No

If the results are incorrect, respond "No". You will then have to switch to the 3270session and reset it to it's previous state in order to continue with the recordingprocess.

If the results are correct, respond "Yes." If this is the first correct result in thissession, you will be asked to supply a file name for the resulting logon script. Allsubsequent script fragments will be appended to this file. If the file already exists,BIMLOGON will append this new script fragment to the end of the existing file.

At his point you can continue the logon process if needed by again selecting dataand answering one or more prompts.

When you are properly signed on, you need to insert the #BYE command. Youdo this by selecting "File" on the menu and choosing "Mark #BYE."

When your script is complete, it is best to test it again just to make sure it willwork correctly with BIM-PC/TRANSFER. First, switch to your 3270 session andlogoff. The 3270 session should now look like it did when you began the scriptrecording. Now switch back to BIMLOGON, select "File" and choose "TryScript..." You will be prompted for the script file name and once selected,BIMLOGON will run the script for you.


Security Overview Page 77

Security OverviewBIM-PC/TRANSFER contains an extensive array of security options that can beput in place to limit what transfers are allowed, and by whom they are allowed.This section contains a brief overview of these options, and directs you to otherparts of this manual for detailed information.

Security for Host Maintenance

All of the security features of BIM-PC/TRANSFER are activated using the “HostCustomization Transaction” referred to in this manual as the “FTRM”transaction. This transaction can actually be any CICS or BIM-TMAN transactionid that you want, and access to this transaction is controlled by the standardCICS or BIM-TMAN transaction and user signon security. This transaction isdescribed in detail starting on page 186.

Since this transaction allows full access to the BIM-PC/TRANSFER security andcustomization features, it should be protected from general use. You mayhowever want some people to be able to view selected portions of the hostoptions with the ability to alter them. To facilitate this, BIM-PC/TRANSFERallows for the definition of up to four (4) additional transaction ids that can havelimited access abilities. This feature is defined in section “ALT MAINT TXNCODES” on page 192.

Security for Transfers

There are many options available within BIM-PC/TRANSFER to protect hostdata against unauthorized access. You can choose which of these options willwork the best in your environment. This section will cover the most commonlyused options.

There are two security modes in which BIM-PC/TRANSFER can operate:

1) Default Security Mode

2) Require User Definition Mode

Default Security Mode

This mode can be used if most of your PC users will require the same type ofsecurity. With this mode, you define a User Definition to be classified as a“Default”, containing the security rules used by the majority of your users. Youthen define individual User Definitions for those specific users that require adifferent set of security options.

Default Security Mode is activated by:


Page 78 Security Overview

1) Setting the “System Options Screen” field “REQUIRE USER DEFINITION”to “N”. See page 191.

2) Creating a “User Definition” to contain the “Default Security” options. Theuser ID can be any value you want, however, the password must be leftblank. See page 201.

3) Supplying the name of the above Default Security User Definition in field“DEFAULT USER DEFINITION” on the “System Options Screen”. See page191.

In this mode, most users will logon to BIM-PC/TRANSFER by leaving the UserID and Password fields blank. This will cause them to use the security optionsdefined for the “Default User”. If the PC user specifies a User ID at logon, BIM-PC/TRANSFER will require that a User definition exist for that ID.

Require User Definition Mode

This security mode requires that all PC users “sign on” to BIM-PC/TRANSFER.This signon process requires a user id and optionally a password to be definedfor each PC user using the host FTRM transaction, and requires that signonauthorization to be activated.

The first step is to require signon authorizaton. This is accomplished by settingthe “System Options Screen” field “REQUIRE USER DEFINITION” to “Y”. Seepage 191. This will require that all PC users enter a valid userid. The “DEFAULTUSER DEFINITION” field is ignored in this mode.

The second step is to define the user ids. This is accomplished by defining one ormore “User Definitions”. Each definition must have a unique user id. The user idcan be up to eight alphanumeric characters, but connot contain imbedded blanks.You can optionally provide a password for each user id. If you leave thepassword blank, BIM-PC/TRANSFER will assume you are using a security exitto validate the password entered by the PC user. Refer to section “UserDefinition Screen” starting on page 201 for detailed information on defining UserDefinitions.

User Security Groups

The primary purpose of the “User Definition” record is to provide a list ofsecurity group names for which each user is authorized. Many of the otherdefinitions created using the FTRM transaction contain a field identified as“SECGRP”. If a non-blank value is specified in these fields, than only userdefinitions containing the same name in its list of “GROUPS” will be able to usethat definition. The definitions that contain the SECGRP are:

• Category Definitions• VSAM Profiles• SAM Profiles• Dataset Access Definitions• Access Security Definitions


Security Overview Page 79

Each User Definition can be authorized for up to forty (40) security group names.Refer to the field “GROUPS” on page 202 for more information.

Dataset Access Security

This type of security is used to protect access to physical datasets or clusters. Itcan be used to protect:

• VSAM Clusters when performing transfers using the “Cluster Name TransferFeature” as described on page 205.

• VSAM Clusters when performing transfers using " REF _Ref439132863 \hBIMFTRDC - VSAM Cluster Driver" as described on page 315.

• Partitioned Datasets (PDS) in MVS.• QSAM Datasets in MVS.• SAM Datasets in VSE.• BIM-EPIC Managed Datasets in VSE.

This protection is activated by creating one or more “Dataset Access Definitions”,and specifying the name(s) of these definitions in the field “DATASET ACCESSUP / DN” in the User Definition(s), and/or for VSAM, the required VSAMProfiles.

Separate Dataset Access definitions are provided for upload access anddownload access. Each definition provides a list of generic dataset name masks.The actual dataset names used in a transfer are matched against each genericmask in the definition, if no match is found, the transfer is rejected.

To allow the same Dataset Access definitions to be shared between multipleusers, individual dataset name masks can be further protected by assigning themto a SECGRP, thus only users authorized for the SECGRP will be authorizedaccess to the mask.

VSAM Security

Access to VSAM Clusters when performing transfers using the “Cluster NameTransfer Feature” of driver BIMFTRDV and the VSAM Cluster driver"BIMFTRDC" are protected using the “Dataset Access Security” described above.VSAM Clusters that are defined via their own unique “VSAM Profiles”, areprotected using the “SECGRP”, and “TYPES” fields. Refer to section “VSAMProfile Definition Screen” starting on page 204 for more information on thesefields.

Access Security Definitions

These definitions are used to protect access to the following:

• BIM-EDIT libraries and members• VSE/LIBR libraries, sub-libraries, and members• VSE/ICCF libraries and members• JES output and held queue entries, and job submissions• POWER queue entries


Page 80 Security Overview

• BIM-PC/TRANSFER scripts contained on the host• CICS Temporary Storage queue entries

These definitions are activated at the “Category Definition” level, and aredefined in detail in section “Access Security Definitions” starting on page 223.


Page 81

USING BIM-PC/TRANSFER


Page 82 Using BIM-PCTRANSFER


Using The PC Transfer Program Page 83

Using The PC Transfer Program - BIMFTR(x)There are two types of PC programs provided with BIM-PC/TRANSFER:

• BIMFTR(x) performs transfers in response to a series of queries andselections by the PC user. This section describes the use of this program.

• BIMAFT(x) is an automated transfer program. The section “Using The PCAutomatic Transfer Program - BIMAFT(x)” on page 107 of this manualdescribes the use of that program.

Four versions of the PC program BIMFTR(x) are provided:

1) a 32-bit version for Microsoft Windows 95/98 or NT (BIMFTRT.EXE)2) a 16-bit version for Microsoft Windows 3.1 or 3.11 (BIMFTR.EXE)3) a 32-bit version for OS/2 2.1 or higher (BIMFTRO.EXE)4) a 16-bit version for MS-DOS or PC-DOS (BIMFTRD.EXE)

Starting the PC Program from within Microsoft Windows 95/98 or NT 4.x

The PC installation procedure created a group, “BIM File Transfer”, within the“Program” section of the “Start” menu. To start the PC transfer process, do thefollowing:

• If you are using an LU2/3270 host connection, start your Windows based3270 emulator. You will need to logon to the CICS or BIM-TMAN systemwhere the mainframe component of BIM-PC/TRANSFER resides. If you areusing BIM-TMAN, you must also select transaction FTRT from the BIM-TMAN menu. This process can be automated by use of a Logon Script. Referto section “Logon/Logoff Scripts” on page 69 for more information.

• If you are using an APPC host connection, BIM-PC/TRANSFER will activatethe emulator automatically.

• Go to the “Start” menu, select the “Programs” group, then select the “BIMFile Transfer” group, and finally select the “File Transfer” entry.

(Proceed to the section titled “Signing On” on page 86.)

Starting the PC Program from within Microsoft Windows 3.1 or NT 3.5.x

The PC installation procedure created a group, “BIM File Transfer”, within theWindows Program Manager. To start the PC transfer process, do the following:

• If you are using an LU2/3270 host connection, start your Windows based3270 emulator. You will need to logon to the CICS or BIM-TMAN systemwhere the mainframe component of BIM-PC/TRANSFER resides. If you areusing BIM-TMAN, you must also select transaction FTRT from the BIM-


Page 84 Using The PC Transfer Program

TMAN menu. This process can be automated by use of a Logon Script. Referto section “Logon/Logoff Scripts” on page 69 for more information.


• Go to the Windows Program Manager, open the “BIM File Transfer” groupand double-click on the “File Transfer” ICON.


Starting the PC Program from within OS/2

The PC installation procedure created an object, “BIM-PC/TRANSFER” on yourOS/2 desktop. To start the PC transfer process, do the following:

• If you are using an LU2/3270 host connection, start your OS/2 based 3270emulator. You will need to logon to the CICS or BIM-TMAN system wherethe mainframe component of BIM-PC/TRANSFER resides. If you are usingBIM-TMAN, you must also select transaction FTRT from the BIM-TMANmenu. This process can be automated by use of a Logon Script. Refer tosection “Logon/Logoff Scripts” on page 69 for more information.

• If you are using an APPC host connection, make sure that yourcommunications manager has been started.

• Go to the OS/2 desktop, open the “BIM-PC/TRANSFER” object and double-click on the “Manual Transfer” ICON.


Starting the PC Program from the DOS Command Line

Starting the transfer program from the DOS command line is a simple two (orthree) step procedure:

• Start your PC DOS 3270 emulator. You will need to logon to the CICS orBIM-TMAN system where the mainframe component of BIM-PC/TRANSFER resides. If you are using BIM-TMAN, you must also selecttransaction FTRT from the BIM-TMAN menu. This process can be automatedby use of a Logon Script. Refer to section “Logon/Logoff Scripts” on page 69for more information.

• Some DOS 3270 emulators require extra steps to load the HLLAPI 3270interface. If yours is one of those, then load the HLLAPI interface. (Forinstance, MultiCom 3270 CUT requires that you execute program MCHAPIfrom the command line to install the HLLAPI interface.)

• Hot-key back to the DOS command line (if you aren't there already) andswitch to the directory containing the PC DOS version of BIM-PC/TRANSFER. Then run program “BIMFTRD.”

There is a limited set of command line options available. These may beentered in any order, separated by spaces if more than one option is chosen.

/G Shifts the display from text to PC graphics mode. This will generate



screens very similar to Microsoft Windows, but its speed willprobably not be acceptable on a PC that is not at least a 100 mHzPentium.

/B Shifts the display to Black & White.

/D For debugging. Use only upon advice from BIM Technical Support.

/Mn Where 'n' is 2,3,4 or 5. Some emulators do not properly report thehost screen size to BIM-PC/TRANSFER. This option can be usedfor those emulators to specify the actual size. The numberrepresents the 3270 model number.



Signing On

If this is the first time you have used this program you will be presented withone or more screen(s) of information concerning host connectivity. This is themost current information about the nuances of using various 3270 and APPCemulators. This information appears automatically the first time you use the PCprogram, for subsequent uses, you will be presented with the sign on screendirectly.

Sign on to File Transfer System

User:

Password:

Exit SettingsOK Help

If this is the first time your are using BIM-PC/TRANSFER, or if you want tochange the type of host connection, select the “Settings” button to display theConnection Settings dialog. Refer to the section “Connecting the PC to the Host”on page 41 for more information on this dialog.

You will need to supply both User and Password to sign on to the File TransferSystem. The User and Password must match one of the user definitions on themainframe. The Password will not display as you key it.

Use the OK button to transmit your sign on request to the mainframe.

The Exit button will immediately terminate the PC program and return you tothe command line, the OS/2 desktop, the Windows Program Manager, oranother OS/2 or Windows open task, depending on which version ofBIM-PC/TRANSFER you are using.

If your user and/or password do not match the values stored on the mainframe,you will receive an error message. You will then be allowed to re-attempt thesign on. If the user and password are matched on the mainframe, the mainTransfer Window will be displayed.

NOTE: depending on the current activity on the host system, the sign on processcan take a few seconds to complete.



PC File Transfer Window

File Transfer Debug Help

Selected Items

Available Items - 4 entries for Category POWER Queue Access

BIM-PC/TRANSFER - PC File Transfer (95/NT)

Upload... Download... Transfer... Accept... Accept All...Select all...

BIMDWDF.LST <-DNLD-- PWR,LST,BIMDWDF 143 LD3 1AUPTS2.LST <-DNLD-- PWR,LST,AUPTS2 5343 LD3 1ALANE2.FTS --UPLD-> EDIT,DDW ,ALANE2 FTSBIMDWDF.ASM <-DNLD-- EDIT,DDW ,BIMDWDF ASMBIMDWDG.ASM <-DNLD-- EDIT,DDW ,BIMDWDG ASM

BIMSPLTX 3968 QD3 1 CMPL 08/11/96 13:18:51 888 21BIMFTRSX 125 QD6 1 07/15/96 20:48:36 3258 74BIMFTRCM 130 QD6 1 07/15/96 20:40:42 2980 63BIMFTRDX 131 QD6 1 07/15/96 20:40:47 2092 53

Job Job Line Page Name Numbr Sfx CDP Rem S CC Form Date Time Count Count

The primary File Transfer Window is split into four sections:

Action Bar This menu provides access to the primary functions of thePC program. The individual entries are discussed in detailbelow.

Tool Bar These buttons provide a quick path to the primary transferfunctions. The processing steps for each of these buttons isdescribed below.

Selected Items This is a list of files that you have selected for upload ordownload processing.

Available Items This is a list of mainframe files that you may select fordownload processing.

Initially, both the Selected Items and Available Items lists are empty. These willbe filled in as you select files for transfer from/to the mainframe.

First, you need to select a file (or files) for transfer. This is accomplished throughthe File pulldown from the Action Bar. Briefly, you need to:

• For download operations, you must first request a list of available files fromthe mainframe. You can then select one or more files for transfer to your PC.

• For upload, you select the PC file you wish to transfer to the mainframe. Youmay select any file that your PC has access to.

Once you have selected a file (or files), you then use the Transfer pulldown fromthe Action Bar. All selected files will be transferred at this time.



File PulldownFile

Exit

Upload . . .

Select all . . .

Settings

Clear all Accept . . . Accept All . . .

Download . . .

This menu is the result of selecting the Fileoption from the Action Bar at the top of theprimary window. You can select this with thePC mouse or by pressing the key combinationALT-F.

The options are:

Download Use this option to begin the download process. Whenselected, a secondary menu will be displayed showing thecategories available for download. The precise contents ofthis secondary menu will vary depending on how you haveset up categories on the mainframe. It can also vary accordingto user/password combination. When you select a category,you will be prompted for selection criteria unique to thecategory (see “Download Selection Dialog” on page 97).

Upload Use this option to begin the upload process. When selected,you will be presented with a file dialog (see File Dialogbelow). When you have selected a PC file for upload, you willthen be asked for the category to upload to and then theidentifying characteristics for the file when transferred to themainframe.

Select all Use this option to select every entry in the “Available Items”list for transfer. You will be prompted once for a file name. Ifyou specify the file name as “*” or “*.ext”, the host file namefor each “Available Items” entry will be used to generateunique filenames for all files selected.

Clear all Use this option to remove all entries from the “SelectedItems” list.

AcceptAccept All

These options will be grayed, not available for use, unless the“Multiple Selection option has been selected from the“Interface Settings Dialog” as described on page 94. Whenthe Multiple Selection option is set, you can select up to 128entries from the “Available Items” section of the MainTransfer Window. After selecting the desired entries, selectone of these buttons or Menu items.

“Accept” will prompt you for destination information foreach of the selected files.



“Accept All” will prompt you once for destinationinformation, and apply it to all of the selected entries.

Settings Use this option to display the Settings Dialog. The followingtypes of settings can be changed:

Connection Settings for the PC connection to the host. Theseare defined on page 42.

General Settings which customize the operation of the PCprogram. These are defined on page 92 .

Log Settings that customize the Transfer Log features of thePC program. These are defined on page 94.

Exit Exits the PC program immediately. No further transfers willtake place.



Transfer Pulldown

Transfer Log

Transfer

Transfer w/LogoffTransfer . . .

This menu is the result of selecting theTransfer option from the Action Bar.

The options are:

TransferChoosing this option will cause all files currently in the selection list to betransferred from or to the host. During the transfer process, you will seea status box showing character and line counts as the file is moved.

Transfer w/LogoffThis option also causes the transfer of all currently selected files to takeplace. In addition, once the transfer is complete, the PC program willlogoff from BIM-PC/TRANSFER and exit - that is, the program will goaway following transfer.

Transfer LogA log entry is maintained for each transfer operation attempted. Certainerror messages are also logged here. Chooses this option to view thetransfer log. The Transfer Log looks like:

Transfer Activity Log

OK Print Log Erase Log Help

8/16/1994 11:54 a.m. DNLD:PWR,LST,BIMCNSOL 126 QD6 -->C:\BIMWND\FTR0\BIMCNSOL

578142 characters, 22 seconds, 26279/sec

8/16/1994 11:54 a.m. UPLD:C:\BIMWIN\FTR0\bimconac.cpp -->EDIT,DDW ,BIMCONAC CPP

29397 characters, 4 seconds, 7349/sec

The four buttons at the bottom of the Transfer Log window are:

OK Exit displayPrint Log Print log on PC printer (not available in DOS version)Erase Log Clear out Transfer LogHelp Help for the window



Help Pulldown

Help Index . . . Error Messages . . .

About

General Help . . . F1

Help This menu appears in response to the Helpoption on the Action Bar.

The options are:

General HelpAttempts to explain the help system used by the PC program. F1 can alsobe pressed at any time for context sensitive help.

Help IndexThe help index is a list of topics that you may select for additionalinformation about the PC program and the transfer process.

Error MessagesDisplays a list of the messages generated by the PC program.

AboutDisplays release information for the version of the PC program you areusing. You will be asked for this information when contacting BIMtechnical support for assistance.

The help displays all look much the same:

BIMFTR - HELP

Exit Index

Help text here

The Help displays are the only secondary windows in the PC product thatcontain a menu. The menu has a possibility of two selections. (The Help Indexdoes not itself contain a selection for the Help Index as it would be redundant.Likewise, Help windows that appear as a result of selection from the Help Indexdo not contain the index menu item.) You can access the menu items with the PCmouse or by the key combination of the ALT key plus the highlighted letter (e.g.the Exit item is accessed by ALT-E).

Exit Close this help window and redisplay whatever was underneath it.

Index Bring up the Help Index.



Dialog Boxes

When the PC program needs additional information from you, it requests thatinformation through the use of dialog boxes. The most commonly used dialogboxes are described below.

General Settings Dialog

The General Settings Dialog appears when you select the “Settings” item fromthe “File” menu, and click the “General” tab.

Connection General Interface Log


Apply Cancel Help Next

Browse

Remember Host SelectionsUse Mainframe Data for File ExtensionsUse 32-bit File BoxAllow FTP AccessUse Connection ProfilesUpload Validation

Default Path

Validation Retry 3

The Settings that can be changed are:

Remember Host Selections

BIM-PC/TRANSFER will remember the selections you made whenquerying the host for file presence, or establishing host file attributes foruploads. You can turn this option off if you wish. This option is includedto retain compatibility with older versions of the PC software which didnot remember host selection information.

Use Mainframe Data for File Extensions

Selecting this option will cause the PC program to initialize the PC filename extension field of the “File Dialog” to values from the selected hostentry, such as POWER queue, or member type, etc.

Use 32-bit File Box

Selecting this option will cause the PC program to use a standardWindows 95/98 File Open Dialog box instead of its own version.



Allow FTP Access

This is a new feature that is still under development. Contact BIMTechnical support for assistance with this option.

Use Connection Profiles

This feature is only available in the 32-bit Windows versions of BIM-PC/TRANSFER (Windows 95/98/NT).

If this feature is activated, the "Connections" tab of this dialog willchange to a "Profiles" tab. The 'Profiles' tab can be used to maintainmultiple connection definitions to one or more host BIM-PC/TRANSFERsystems.

Clicking this option on/off will not immediately change this dialog. Youwill need to set the option as you want it to be, press 'Apply', and thenre-enter the "Settings" process to proceed with the "Profiles" dialog.

Refer to section "BIM-PC/TRANSFER Connection Settings" on page 42for more information on the "Profiles" dialog.

Upload Validation

If this feature is activated, all uploads that use an LU2 connection to thehost will utilize ‘checksum’ processing to validate each buffertransmitted from the PC to the host. The ‘Validation Retry’ count shouldbe set to the number of retries of a buffer transmission before the transfershould be canceled.

This option is not needed unless you have a remote connection betweenyour PC and the host, and the modems you are using do not performtheir own error correction processing. Activating this option will addprocessing overhead at both the PC and the host that may affect yourtransfer rate.

Default Path

BIM-PC/TRANSFER will download to and begin its upload search fromthe directory that contains the executable (.EXE) program. You can causeBIM-PC/TRANSFER to look into another directory by keying its fullpath specification here (e.g. C:\BIMWIN\FTR). This option is alsoavailable from the command line by entering the full path name (e.g.BIMFTRD C:\BIMWIN\FTR). You can click the “Browse” button tosearch for the desired path.



Interface Settings Dialog

The Interface Settings Dialog appears when you select the “Settings” item fromthe “File” menu, and click the “Inteface” tab.

Connection General Interface Log



Multiple SelectionRetainTransfer Errors

The Settings that can be changed are:

Multiple Selection

This option activates or deactivates the “Accept” and “Accept All”options on the Tool Bar and the File Menu. Refer to section “FilePulldown” on page 88 for more information about these options.

Retain Transfer Errors

When this option is checked, transfers that do not complete successfullyremain in the “Selected Items” section of the Main Transfer Window sothat the problem can be corrected, and the transfer reattempted. If thisoption is not checked, all entries are removed from the “Selected Items”section after completion.



Log Settings Dialog

The Log Settings Dialog appears when you select the “Settings” item from the“File” menu, and click the “Log” tab.




Create Transfer LogTransfer Log to FilePrint Log on Exit

Transfer Log File Name BIMFTR.LOG

The options that can be changed are:

Create Transfer Log

BIM-PC/TRANSFER creates a transfer log summarizing each transferbetween the PC and host. You can turn this off if you wish. (The “/NL”option on the command line can also be used to turn off logging.) If youturn this option off, the next two options will be ignored.

Transfer Log to File

The transfer log can be written to a PC file if so desired. The file namethat will be used is shown below. New transfers are always appended tothis PC file. (The “/L” option on the command line can also be used todirect the transfer log to a PC disk file.)

Print Log on Exit

You can optionally cause the transfer log to be printed when exitingeither BIMFTR(D/O) or BIMAFT(D/O). This option is mutuallyexclusive with the “Transfer Log to File” option described above. (The“/P” command line option will accomplish this as well.)

Transfer Log File Name

If you select “Transfer Log to File” above, you may also change the nameof the transfer log file. The default name is “BIMFTR.LOG.”



File Dialog

The File Dialog appears at several different points within theBIM-PC/TRANSFER program:

• Used to select a PC file for upload transfer.

• Appears in response to the change file name request.

File Name:

Directory: C:\BIM\WIN\FTR

Directories Files

. . BIM1.TXTBIM2.ASCBIM3BIM4STUFBIM5BIM6BIM7

File Name

OK

Drives

A:B:C:D:

Cancel Help

Script FileUnique Upload

With this dialog you can point to any file accessible by your PC.

File Name Identifies the PC file. You may key directly into it if youwish, or you can use the list boxes in the middle of thedialog box to locate the file/drive/directory.

If this dialog is being displayed for an upload transfer, youcan specify a generic PC mask for the file name. This willcause all matching PC files to be selected for transfer. If the“Unique Upload” option is selected, the matching files willbe moved to the “Selected Items” list for transfer to uniquehost destinations. If the “Unique Upload” option is notselected, all matching PC files will be transferred to a singlehost destination.

Directory Cannot be keyed into. It will change as you navigatethrough the PC disk(s) using the “Directories” list box in thecenter of the dialog.

The three list boxes in the middle of the dialog allow you to navigate through thePC drive/directory structure to locate the file name (or target directory fordownloads). You can click with the mouse on whatever you wish to change, orwith the keyboard, TAB to the relevant list box, use the arrow keys to position onan entry and press ENTER to select it. The three list boxes are:



Drives Used to select the PC disk drive.Directories Used to select the directory.Files Used to select an individual file.

Script File This check box is used to indicate that the selected PC file isan upload script. Refer to the section “File Upload Scripts”on page 174 for more information.

Unique Upload This check box is used when a generic value is specified for“File Name”. Refer to the description of “File Name” aboveand the section “Generic Uploads Using the Unique Option”on page 103 for more information.

Download Selection Dialog

Once you have selected a mainframe category to download from, you will bepresented with a dialog box requesting identifying information for the particularcategory. The exact contents of this dialog will vary from one category to thenext. The illustration below shows the selection dialog for access to the VSElibraries.

Library.Sublib:

Member:

Type:

Download Script Name

VSE Library Access

OK CancelDefaults Help

The data entry fields displayed depend on the category chosen. (Here, the VSElibrary access allows for selection by Library.Sublib, member name and membertype.) One or more of the fields may be required (for VSE library access, theLibrary.Sublib is required).

Use the data entry fields to qualify your search for matching files on themainframe. For instance, rather than obtaining a list of the entire contents of theVSE Library.Sublib, you might want to restrict the resulting list by type (.OBJperhaps), or name (e.g. AP* to select all members beginning with the letters“AP”).

Generic selection is allowed for most fields that are shown in the DownloadSelection Dialog. BIM-PC/TRANSFER recognizes two different wild-cardcharacters:

* is for any number of any kind of character, and+ a single character of any kind.



For example, assume the following members on the host: BIMINDMD,BIMBMSMD, BIWXPCMD, DDWXXXMX, KEFMDFXM. Some wild-card entriesand their results are shown below:

WildCard Selects *MD BIMINDMD BIMBMSMD BIWXPCMD*MD* BIMINDMD BIMBMSMD BIWXPCMD KEFMDFXMDDW* DDWXXXMX*M* BIMINDMD BIMBMSMD BIWXPCMD DDWXXXMX KEFMDFXM++++++M+ BIMINDMD BIMBMSMD BIWXPCMD DDWXXXMXBIM*M - n o n e -BI+*M+ BIMINDMD BIMBMSMD BIWXPCMDBIM*MD BIMINDMD BIMBMSMD

The PC Help provided in the program describes the various fields provided foreach of the mainframe drivers and their entry requirements.

When you have made your selections, press the OK button to transmit yourrequest to the mainframe. Depending on your environment, this can take severalseconds to complete. The list of matching mainframe files that match yourselections will be placed in the “Available Items” list on BIM-PC/TRANSFER'smain window. You may then select individual files from that list for download toyour PC.

Generic LIBQUE Values for Downloads

The first field in each Download Selection Dialog is referred to by BIM-PC/TRANSFER as the “LIBQUE”. This is typically the name of a library or queuefrom which a directory of items can be obtained. In the above example, theLIBQUE field is the “Library.Sublib”.

For most download requests, this field can be specified as a generic value, asdescribed above. When a generic is specified, a special dialog is generated on thePC containing a list of the matching LIBQUE values. The PC user selects thedesired LIBQUE from the list, and the host will then complete the downloadquery.

The following types of transfers can specify generic LIBQUE values fordownloads:

• VSAM Cluster transfers using driver BIMFTRDC. For MVS, the genericcluster name must contain the complete high-level qualifier.

• PDS transfers using driver BIMFTRDD. The generic PDS name must containthe complete high-level qualifier.

• BIM-EDIT transfers using driver BIMFTRDE.

• VSE library transfers using drivers BIMFTRDL or BIMFTRDR. Only the‘sublib’ can be specified as generic.

• QSAM transfers using driver BIMFTRDQ. The generic dataset name mustcontain the complete high-level qualifier.

• VSE SAM datasets.



• BIM-EPIC managed datasets.

• VSAM Transfers using driver BIMFTRDV.

Defaults Button

This button is only active (non-gray) for selected categories. If active, when it ispressed it will display the “Category Defaults” dialog. The defaults dialog allowscategory specific transfer options to be selected as defaults for all matchingmainframe files that are placed in the “Available Items” list. Options for specifictransfers can be specified, and/or overridden on the “Download DestinationDialog” using the “Category Options” button.

Download Script Name

All of the Download Selection Dialogs contain a field named “Download ScriptName”. It is either contained in the Download dialog itself, as shown above, or itis contained in the “Defaults” dialog, accessed by pressing the “Defaults” button.The Download Script Name field is used if you have a “Download Script” on thehost that you want to use to format the data for this category. The script specifiedin this field will be used for all transfers requested from the entries contained inthe “Available Items” list that results from this dialog.

Download Destination Dialog

When you select a file for download from the mainframe to the PC, you will bepresented with the following dialog. This dialog allows you to determine whereto put the file on the PC and how to handle the transfer process.

Download File From Host

Duplicate Files Replace File Cancel Transfer Rename File Append File

ASCII Yes No Default

CR/LF Yes No Default

LRECL: 0

File Name: BIMFTRSX

Directory: C:\BIMWIN\FTR

OK Cancel Help

Change File Name Category Options

BIM-PC/TRANSFER attempts to name the PC file using the most likelycandidate from the category selection list (e.g. for the VSE libraries, this will bethe library member name). If this is not OK, then pressing the “Change FileName” button will present you with the File Dialog described on page 96.



In addition to file name, you can also control how duplicate files are handled,only one of which may be chosen for a particular transfer. There are four options:

Replace File BIM-PC/TRANSFER will replace whatever is currently onthe PC with the new information from the mainframe. This isthe default option.

Cancel Transfer The transfer operation will be canceled for this file.

Rename File The newly downloaded file will be renamed so as not todelete an existing file. The rename process changes theextension portion of the PC file name. For example, if youdownload several copies of a file named “GORPHIN”, theywill be written to the PC as “GORPHIN,” “GORPHIN.1”,“GORPHIN.2,” etc.

Append File Append the downloaded text to the end of the existing PCfile.

There are three things you may alter to control the transfer process itself: ASCII,CR/LF and LRECL.

ASCII

These three options determine how mainframe data are treated during thetransfer process. Choose one of:

Yes Host data will be translated from EBCDIC to ASCII prior to transferto the PC. Use this for text files.

No Host data will not be translated prior to transfer to the PC.

Default The transfer driver program running on the host will determine thecorrect translation option to use for this transfer. This is the defaultoption for transfers from the host to the PC and should be correct formost transfer operations.

(See “ASCII Translation Option” on page 104 for more information.)

CRLF

These three options are used to tell the mainframe how to handle lines during thetransfer process. Choose one of:

Yes A carriage-return line-feed pair will be inserted by the host programbetween each line of data.

No The host will not insert a carriage-return line-feed pair between lines.This selection will result in fixed length data lines from the host. Thelength of these lines will vary depending on driver being used, or youmay specify it using the LRECL option.

Default The transfer driver program running on the host will determine theproper setting for this option. This is the default and should becorrect for most transfer operations.



(See “CRLF Transfer Option” on page 105 for more information.)

LRECL

This allows you to tell the mainframe what the assumed line length is for thistransfer. Use this option if you specified “No” for CR/LF above. With CR/LFspecified as “Yes,” this option is ignored.

Category Options Button

This button is only active (non-gray) for selected categories. If active, when it ispressed it will display the “Category Options” dialog. The options dialog allowscategory specific transfer options to be specified. These options override, for theselected entry, the default options that were specified on the “DownloadSelection Dialog”.

Upload Selection Dialog

When you select one or more file(s) for upload to the mainframe, you must nextselect the category to upload the file into. After the category is chosen, you willthen receive a dialog that looks similar to the one shown below.

Library.Sublib:

Member: BIMCONCT

Type: OBJ

Data in PROC (Y/N):

VSE Library Access

Duplicate Files Replace File New Append

ASCII Yes No Default

CR/LF Yes No Default

LRECL: 0

N

OK HelpCancel

The data entry fields displayed depend on the category chosen. (Here, the VSElibrary access allows for selection by Library.Sublib, member name and membertype.) One or more of the fields may be required (for VSE library access, theLibrary.Sublib, name and type are required for uploads).

This dialog has a dynamic look and feel. For some categories, there are too manydata entry fields for the three control boxes (Duplicate Files, ASCII and CR/LF)to fit below the entry fields. Depending on the category chosen, you may seethem along the right-hand side of the dialog. Their function remains the sameregardless of where they are placed on the screen.



If you page back to the Download Selection Dialog (page 97) you will notice thatan extra field is present here. This is not unusual, the actual fields shown canchange depending on the transfer direction (upload as opposed to download).

Generic LIBQUE Values for Uploads

The first field in each Upload Selection Dialog is referred to by BIM-PC/TRANSFER as the “LIBQUE”. This is typically the name of a library or queueinto which the specified upload will be sent. In the above example, the LIBQUEfield is the “Library.Sublib”.

For most upload requests, this field can be specified as a generic value. When ageneric is specified, a special dialog is generated on the PC containing a list of thematching LIBQUE values. The PC user selects the desired LIBQUE from the list,and the host will then complete the upload request.

The following types of transfers can specify generic LIBQUE values for uploads:

• VSAM Cluster transfers using driver BIMFTRDC. For MVS, the genericcluster name must contain the complete high-level qualifier.

• PDS transfers using driver BIMFTRDD. The generic PDS name must containthe complete high-level qualifier.

• BIM-EDIT transfers using driver BIMFTRDE.

• VSE library transfers using drivers BIMFTRDL or BIMFTRDR. Only the‘sublib’ can be specified as generic.

• QSAM transfers using driver BIMFTRDQ. The generic dataset name mustcontain the complete high-level qualifier.

• VSAM Transfers using driver BIMFTRDV.

• VSE SAM datasets.

• BIM-EPIC managed datasets.



Generic Uploads Using the Unique Option

If you specify a generic file name on the File Dialog, and you also select the“Unique Upload” option, you will need to provide instructions on this dialog forBIM-PC/TRANSFER to use to generate unique mainframe names for each of thePC files to be uploaded. These instructions are provided in the form of variablekeywords that can be specified in which ever dialog fields are needed or desiredto uniquely identify each uploaded entry. Any combination of the followingkeyword variables can be specified:

Variable 32-bit Windows & OS/2 16-bit Windows & DOS

%LNM Long File Name 8 character file name

%SNM System Short File Name 8 character file name

%GNM Long File Name with spacesremoved and truncated to 8characters

8 character file name

%FNM Long File Name Full File Name includingextension

%EXT File extension

%DAT The uploaded file date. This is always 10 characters long and willvary depending on your PC’s system settings. The format will beone of: mm-dd-ccyy, ccyy-mm-dd,or dd-mm-ccyy.

%TIM The PC file creation time expressed as hh:mm:ss.

Duplicate Files

In addition to specifying the mainframe file name, you may also chose how themainframe is to treat duplicate files. There are three mutually exclusive options:

Replace FileThe mainframe file will be replaced with the newly uploaded data.

NewA new file will be created on the mainframe.

AppendThe uploaded information will be appended to the existing mainframefile if one already exists, otherwise a new file will be created.

The exact processing for each of these options varies according to the category.(For instance, all uploads to POWER will be treated as “New” regardless of yoursetting here.) See section “Driver Specifications” starting on page 306 for moreinformation.



There are three things you may alter to control the transfer process itself: ASCII,CR/LF and LRECL.

ASCII

These options determine how mainframe data are treated during the transferprocess. Choose one of:

Yes Data will be translated from ASCII to EBCDIC by the host uponreceipt.

No Data will not be translated.

Default Not available for upload.

(See “ASCII Translation Option” below for more information.)

CRLF

These options are used to tell the mainframe what to expect between lines duringthe transfer process. Choose one of:

Yes The mainframe will expect a carriage-return line-feed between lines.

No The host will not expect a carriage-return line-feed pair betweenlines. Instead, the host will assume that the input has a fixed linelength. This assumed line length varies depending on the driverbeing used.

Default Not available for upload.

(See “CRLF Transfer Option” below for more information.)

LRECL

This allows you to tell the mainframe what the assumed line length is for thistransfer. Use this option if you specified “No” for CR/LF above. With CR/LFspecified as “Yes,” this option is ignored.

ASCII Translation Option

The PC stores character data in ASCII format. The mainframe stores characterdata in EBCDIC format. The two formats do not resemble each other in any way.

As a general rule, mainframe text data needs to be converted from EBCDIC toASCII for use by a PC. Likewise, PC text data needs to be converted from ASCIIto EBCDIC for use by the mainframe. Most often, when transferring text files, thisoption should be set to “Yes”. If you are transferring VSAM files, for example,this option should most likely be set to “No” - but not always.

It is generally best to leave this setting at “Default”. Then the mainframe driverprogram decides what the proper translation scheme should be.



CRLF Transfer Option

This option tells the mainframe how it is to handle individual lines of data whendownloading, and what to assume about them when uploading.

Set to “Yes”, the mainframe will insert a carriage-return line-feed pair betweeneach data line on download. On upload, the “Yes” setting tells the mainframedriver program to expect a carriage-return line-feed between each incoming line.

Set to “No”, the mainframe will not insert a carriage-return line-feed pair into thedownload data. Instead, on download the mainframe driver program will sendfixed length data lines, padding out the line with spaces as needed. If you areusing the “No” option with text data, whatever program you use to process theresulting file on the PC will need to know about the fixed length format of thefile. (For BIM supplied drivers, the line lengths are 80 bytes for everything butthe POWER LST queue, where the line length is 132 bytes.)

On upload, a “No” setting tells the mainframe to avoid looking for carriage-return line-feed pairs and instead to assume the input is in fixed length format(80 for everything but POWER LST which is 132).

You can get into some trouble using the wrong option. It is best to leave thesetting at default for downloads and let the mainframe driver program preparethe data in the proper format.

Some examples of the BIM supplied drivers and their processing options aregiven below:Host Access Download Upload Line Length

POWER/VSE Queue=LST Yes Yes 132

POWER/VSE Queue=RDR Yes Yes 80

VSE Library Type=C Yes Yes 80

VSE Library Type=OBJ No No 80

VSAM Access No No N/A

Refer to the section “Driver Specifications” starting on page 306 for a completelist of options and default line lengths.



Transfer Status Dialog

The following dialog will be displayed during each transfer:

Transferring: PWR.LST.BIMCNSOL 10012 LD3 4

To: C:\BIMWIN\FTR0\BIMCNSOL

Characters:

Buffers:

Characters/second:

Lines:

Cancel

BIM PC/TRANSFER Transfer Status

167582

7

33516 00:03:14

1657

32%

Elapsed:

This dialog is updated periodically during the transfer to show the progressbeing made.

The accuracy of the percentage bar will vary depending on the type of thetransfer:

• Uploads will be the most accurate.

• Percentages are not available for QSAM downloads, VSE SAM downloadsand PDS downloads from members that do not have the standard ISPFdirectory format.

• BIM-EPIC managed datasets will be an estimate of the actual size. The largerthe dataset, the closer the estimate will be.

• VSAM downloads will be the least accurate. BIM-PC/TRANSFER usesinformation from the VSAM catalog to determine file size.

• All other transfers should be fairly accurate as to the percentage complete.

If the amount of data being transferred cannot be determined, the percentage barwill display as “Unavailable”.


Using The PC Automatic Transfer Program Page 107

Using The PC Automatic Transfer Program - BIMAFT(x)BIM-PC/TRANSFER includes an Automatic File Transfer program which allowsyou to setup transfers, both downloads and uploads, which will occurautomatically (perhaps overnight).

Four versions of the Automatic Transfer program BIMAFT(x) are provided:

1) a 32-bit version for Microsoft Windows 95/98 or NT (BIMAFTT.EXE)2) a 16-bit version for Microsoft Windows 3.1 or 3.11 (BIMAFT.EXE)3) a 32-bit version for OS/2 2.1 or higher (BIMAFTO.EXE)4) a 16-bit version for MS-DOS or PC-DOS (BIMAFTD.EXE)

The Automatic File Transfer program can operate in one of three modes:

1) Basic mode. Unless otherwise stated, this section will be discussing this modeof operation.

2) Host mode. This is the mode it is in for HOSTAFT processing. The section“Host Initiated Automatic File Transfer (HOSTAFT)” starting on page 159discusses HOSTAFT processing in detail. This section will discuss HOSTAFTprocessing at each menu and dialog that is affected.

3) Combined mode. In this mode, HOSTAFT mode is entered between passes ofthe script being processed in “Basic mode”. This allows a PC to have anAutomatic Transfer Script of its own that it is processing, and at the sametime, query the host for additional work that it needs to perform. Combinedmode is entered by specifying “Query Host on Pause/end” in the “ProgramOptions” dialog.

The Automatic File Transfer program is provided in a Microsoft Windowsversion, an OS/2 version, and a PC DOS version. The Windows component(BIMAFT.EXE) requires Microsoft Windows version 3.1 or higher. The OS/2component (BIMAFTO.EXE) requires OS/2 version 2.1 or higher. The PC DOScomponent (BIMAFTD.EXE) requires a 286 or better PC with a minimum of 2 MBof RAM.

Automatic File Transfer “Basic mode” processing is driven by a script file thatyou create. You can key the script file using your favorite PC text editor, or youcan interactively create one using the RECORD feature of BIMAFT. Beforeattempting to create a script, you should familiarize yourself with the BIM-PC/TRANSFER process by using BIMFTR to manually perform several transferslike those you wish to automate.

BIMAFT will work its way through the entire script attempting to transfer eachfile contained within. For each file, BIMAFT will first check to see if the file isavailable. If the file is available (e.g. present in the POWER queue on the host), itwill be transferred. If the file is not yet available, BIMAFT will attempt to process


Page 108 Using The PC Automatic Transfer Program

any remaining files in the script. At the end of the script, if one or more files werenot transferred, BIMAFT will wait for a minute (or more, see the #OPTIONstatement below) and then start over at the top of the script. This will continueuntil: (1) you cancel the process, (2) all files listed in the script have beensuccessfully transferred, or (3) the retry limit (see #OPTION statement below)you have specified in the script has been exceeded.

A file will be transferred only once. Following successful transfer, BIMAFT willignore that file in succeeding passes (if any) through the script file.

All transfer activity is logged by BIMAFT in a fashion similar to the log formanual transfer, BIMFTR. You can use this log to verify that all transfer activitytook place.

An Automatic Transfer Script can contain any number of download and/orupload requests in any combination.

Starting BIMAFT(x) from within Microsoft Windows 95/98 or NT 4.x

The PC installation procedure created a group, “BIM File Transfer”, within the“Program” section of the “Start” menu. To start the automatic transfer process,do the following:



• Go to the “Start” menu, select the “Programs” group, then select the “BIMFile Transfer” group, and finally select the “Auto Transfer” entry.

You can have BIMAFT start with a specific script by making a copy of the AutoTransfer Program Item and adding the script file name to the end of theCommand Line, following the BIMAFTT.EXE. When this new Program Item isstarted, BIMAFT will initiate in a minimized state and begin executing the script.

Starting BIMAFT(x) from within Microsoft Windows 3.1 or NT 3.5.x

The PC installation procedure created a group, “BIM File Transfer”, within theWindows Program Manager. To start the PC transfer process, do the following:





• Go to the Windows Program Manager, open the “BIM File Transfer” groupand double-click on the “Auto Transfer” ICON.

You can have BIMAFT start with a specific script by making a copy of the AutoTransfer Program Item and adding the script file name to the end of theCommand Line, following the BIMAFT.EXE or BIMAFTT.EXE. When this newProgram Item is started, BIMAFT will initiate in a minimized state and beginexecuting the script.

Starting BIMAFTO from within OS/2

The PC installation procedure created an object, “BIM-PC/TRANSFER” on yourOS/2 desktop. To start the automatic transfer process, do the following:

• If you are using an LU2/3270 host connection, start your OS/2 based 3270emulator. You will need to logon to the CICS or BIM-TMAN system wherethe mainframe component of BIM-PC/TRANSFER resides. If you are usingBIM-TMAN, you must also select transaction FTRT from the BIM-TMANmenu. This process can be automated by use of a Logon Script. Refer tosection “Logon/Logoff Scripts” on page 69 for more information.


• Go to the OS/2 desktop, open the “BIM-PC/TRANSFER” object and double-click on the “Automatic Transfer” ICON.

You can have BIMAFT start with a specific script by making a copy of the AutoTransfer object and adding the script file name to the “Parameters” box of theobject. When this new object is started, BIMAFT will initiate in a minimized stateand begin executing the script.

Starting BIMAFTD from the DOS Command Line

Starting the automatic transfer program from the DOS command line is a simpletwo (or three) step procedure:

• Start your PC DOS 3270 emulator. You will need to logon to the CICS orBIM-TMAN system where the mainframe component of BIM-PC/TRANSFER resides. If you are using BIM-TMAN, you must also selecttransaction FTRT from the BIM-TMAN menu. This process can be automatedby use of a Logon Script. Refer to section “Logon/Logoff Scripts” on page 69for more information.

• Some DOS 3270 emulators require extra steps to load the HLLAPI 3270interface. If yours is one of those, then load the HLLAPI interface. (Forinstance, MultiCom 3270 CUT requires that you execute program MCHAPIfrom the command line to install the HLLAPI interface.)



• Hot-key back to the DOS command line (if you aren't there already) andswitch to the directory containing the PC DOS version of BIM-PC/TRANSFER. Then run program “BIMAFTD.”

You can have BIMAFTD start with a specific script by specifying the scriptfile name on the command Line, following the BIMAFTD.EXE.

There is a limited set of command line options available. These may beentered in any order, separated by spaces if more than one option is chosen.

/G Shifts the display from text to PC graphics mode. This will generatescreens very similar to Microsoft Windows, but its speed willprobably not be acceptable on a PC that is not at least a 486.

/B Shifts the display to Black & White.

/D For debugging. Use only upon advice from BIM Technical Support.

/Mn Where 'n' is 2,3,4 or 5. Some emulators do not properly report thehost screen size to BIM-PC/TRANSFER. This option can be usedfor those emulators to specify the actual size. The numberrepresents the 3270 model number.



BIMAFT(x) Main Program Window

File Process Debug Help

BIM-PC/TRANSFER - Automatic File Transfer

ExecuteOpen Cancel ExitNo File Selected

This is the main window for the Automatic Transfer Program. In addition to themenu across the top, buttons exist for four of the most commonly used functions:

Open Load a script file for processing.

Execute Run a script.

Cancel Cancel script processing.

Exit Terminate the program.

When a script file has been loaded it will be displayed in the text box that makesup the bulk of the window. Limited editing capabilities are available for theloaded script. You may modify the loaded script, add or delete lines from it. Thistext box is limited to a maximum of 32,767 (I wonder where that number camefrom) bytes of script information. If your script is larger than this, you will needto use a separate text editor to create and/or modify it. Most scripts willcomfortably fit within this maximum.

Many of the secondary dialogs that you will encounter when using this programare the same as those for manual transfer (BIMFTR) documented earlier in thismanual. This did not happen by accident. The two programs share the same codefor common transfer activities. Where the dialogs are duplicated in the discussionbelow, you will be referred back to the discussion for manual transfer.



File Pull Down

Enter Host ModeHost status . . .

Exit

Upload Script to Host . . .Save Signon to File . . .

Transfer Log . . .

FILE

Open Script File . . .

Settings

NewSave Script file . . .

This menu results from selecting the Fileoption from the menu bar. You can selectthis with the PC mouse or by pressing thekey combination ALT-F.

The options are:

Open Script File ... Select this entry to load a script file from PC disk. Thisfunction can also be activated by using the “Open”button from the main window. In response to thisselection, BIMAFT will present a File Dialog Box (seediscussion above) to assist you in selecting the file youwish to load.

New ... Select this entry to create a new script file. If you havealready loaded a script file, you will be prompted forsave information.

Save Script File ... Select this entry to save the currently loaded script fileto PC disk. You will always have the option ofchanging the file name if you desire.

Upload Script to Host ... Select this entry to begin a file upload process toupload the current script to the host. This process canbe used when you use the “record” feature to generatea HOSTAFT Script, which needs to be transferred tothe host before it can activated. Standard uploaddialogs, as discussed for program BIMFTR, will bepresented. You will need to select a Category that youhave previously defined to work with driver“BIMFTRDX” to upload the script.

Save Signon to File ... Select this entry to display a dialog that is used tocreate a Signon file. The created file can be used in a#SIGNON statement. Refer to “Signon Dialog” on page121 for more information.

Enter Host Mode Select this entry to leave “Basic mode” processing andenter “Host mode” processing. Refer to section“Activating/Deactivating HOSTAFT on The PC”starting on page 162 for more information. To leave“Host mode”, either press the “CANCEL” button onthe main window, or select “Exit” from this menu.



Host status ... Select this entry while in “Host mode” to view the“Host Initiated Transfer Status Dialog”. This dialogprovides a trace history of the HOSTAFT functions thathave been performed. This could be useful for problemdetermination.

Transfer Log ... The Transfer Log for BIMAFT is similar to the TransferLog documented on page 90 for BIMFTR.

Settings Use this option to display the Settings Dialog. Thefollowing types of settings can be changed:

Connection Settings for the PC connection to the host.These are defined on page 42.

General Settings which customize the operation of thePC programs. These are defined on page 92 .

Auto Settings which customize the operation of the PCAFT program. These are defined on page 115.

Log Settings that customize the Transfer Log featuresof the PC program. These are defined on page 94.

Exit Exit the program.

Process Pulldown

Activate Host Transfer

Record . . .

Execute

Process This menu results from selection of theProcess option on the menu bar. You canselect this with the PC mouse or bypressing the key combination ALT-P.

The options are:

Execute This selection will cause execution of a script file. If a fileis currently loaded, it will be processed. If a file is notloaded, you will be prompted for a file name using a FileDialog Box (see BIMFTR above).

Record This selection starts the record process. This is the easyway of creating a script file (see Script Recording belowfor more information).



Activate Host Transfer This selection displays the following dialog:


OK Cancel Help

Script

Job Name

User Parms

This dialog can be used to activate a HOSTAFT Script forprocessing It contains the same fields as the “HOSTAFTActivate Script Screen” described on page 249. Thisdialog will normally be used for testing new HOSTAFTScripts.

Help Pulldown

Help Index . . .

Error Messages . . .

About

General Help . . . F1

Help This menu appears in response to the Helpoption on the Action Bar.

The options are:

General HelpAttempts to explain the help system used by the PC program. F1 can alsobe pressed at any time for context sensitive help.

Help IndexThe help index is a list of topics that you may select for additionalinformation about the PC program and the transfer process.

AboutDisplays release information for the version of the PC program you areusing. You will be asked for this information when contacting BIMtechnical support for assistance.



Auto Settings Dialog

The Auto Settings Dialog appears when you select the “Settings” item from the“File” menu, and click the “Auto” tab.




Query Host on Pause/endIgnore Incomplete ScriptEnable Rapid Reload

Suppress MessagesSuppress Status

Host Transfer Wait (min.) 10

Quit On Completion

Yes No Warn

The settings that can be changed are:

Query Host on Pause/end

If this option is on, BIMAFT(D/O) will begin operating in “Combinedmode”. That is, when each pass of an Automatic File Transfer Script hasbeen completed, BIMAFT(D/O) will query the host as if it were in “Hostmode” searching for any additional work to be performed. If any isavailable, the current script will be “suspended”, and the HOSTAFTScript will be processed. After it has been completed, the “suspended”script will be resumed for the next pass.

Ignore Incomplete Script

This option is used by the Host Initiated Transfer process to ignore errorsthat otherwise would have been generated when one or more transferscannot be completed. If this option is left off, an error report will begenerated for all uncompleted transfers.

Enable Rapid Reload

This option should normally be on. If you experience problems due toyour script restarting too quickly, try turning this option off.

Suppress Messages

This option is only used when BIMAFT(x) is running in a “minimized”state. If this option is on, error messages generated during the transfer



will only be written to the “Transfer Log”. If this option is off, an errordialog will also be generated that requires a response from the PC user.

Suppress Status

This option is only used when BIMAFT(x) is running in a “minimized”state. If this option is on, no “

Transfer Status Dialog” will be displayed during the transfer. The “

Transfer Status Dialog” is described on page 106.

Quit On Completion

‘Yes’ BIMAFT(x) will terminate upon completion of script processing.

‘No’ BIMAFT(x) will display the transfer log and wait for subsequentoperator intervention at the end of script processing.

‘Warn’ If no errors are encountered, the Automatic Transfer Programwill terminate upon completion of script processing. If one ormore errors are encountered, a warning message will bedisplayed and BIMAFT(x) will not terminate.

Host Transfer Wait (min.)

This field is used when running in “Host mode” to specify the amount oftime, in minutes, that the PC should wait between each query to the hostfor work to be performed. The default is one minute. If you have a largenumber of PC’s , you may want to increase this value to reduce the loadon the host system.



Script Recording

Script File Recorder

Generate Automated Transfer Script File

Signon...

Download...

Upload...

Exec

Start Host TransactionStart

Define Name SkeletonDefineName

(Host Transfer) Send to NetnameSendto

Activate Host TransferActivate

Automatic Transfer OptionsOption

End of Script FileEnd... PC-DOS CommandDOS Command

Check for file presenceIfexists

Check for file absenceIfnotexists

Terminate preceding IFEXISTSEndif

Sign on to Host

Download File From Host

Upload File to Host

Execute PC Program

Cancel

The record process is started by selecting “Record” from the Process pull down.There are thirteen options related to Automatic Transfer and/or HOSTAFTScript generation:

Signon Your script must contain at least one signon in order to access thetransfer capabilities of BIM-PC/TRANSFER. Click on this buttonto generate a signon to the host. Refer to section “Signon Dialog”on page 121.

Download Click on this button to set up a download process.

Upload Use this button to establish an upload process in your script.

Exec Click this button to establish a PC program execution within yourscript. This button is not available in the DOS version. Refer tosection “Execute PC Program Dialog” on page 122 for moreinformation.

Sendto • If you are recording a HOSTAFT Script, use this button todisplay a dialog where you can enter the VTAM netnames ofthe PC workstations that are to receive this script when it isactivated on the host. This should be the first action youperform when recording a HOSTAFT Script. Refer to section “

Host Transfer Send to Netname Dialog” on page 124 for moreinformation.



Start Click this button to display the following dialog:

Start Host Transaction

OK Cancel Help

Host Transaction

Network Name

Request Id

Time (hhmmss)

Request Data

Interval

This dialog can be used generate a #START statement in yourscript. Refer to page 144 for information on that statement.

DefineName Click this button to generate a module #DEFINENAME statementfor a specific host Category. You will first be presented with a signon dialog. Enter your userid and password to signon to the hostside of BIM-PC/TRANSFER. You will then be presented with adialog containing all of the host Categories you are authorzied touse. Select the desired category. A query dialog will then bepresented, simply press OK to cause the host query to occur. Thisquery is performed to retrieve the fields that are available for thisCategory. Refer to section “#DEFINENAME” on page 148 formore information.

Ifexists Use this button to establish a file existence test for a group of oneor more transfers. This allows a group of transfers to be performedonly if a specific file exists. The group of transfers is terminated bythe “Endif” button.

After you have established this test, use the “Download” and/or“Upload” buttons to define the transfers to be contained in thegroup, and finally press the “Endif” button to terminate the group.

Ifnotexists Use this button to establish a file absence test for a group of one ormore transfers. This allows a group of transfers to be performedonly if a specific file does not exist. It otherwise works just like the“Ifexists” button.

Endif Use this button to terminate a group of transfers that was startedwith either the “Ifexists” or “Ifnotexists” buttons.

Option Click this button to display the “Automatic Transfer Options”dialog. This dialog is where you can specify all of the processingoptions available for Automatic Transfers. Refer to section“Automatic Transfer Options Dialog” on page 123 for moreinformation.

Activate Click this button to display the following dialog:




OK Cancel Help

Script

Job Name

User Parms

This dialog can be used generate a #HOSTAFT statement in yourscript. Refer to page 143 for information on that statement.

DOSCommand

Click this button to display the following dialog:

PC-DOS Command

OK Cancel

Browse

Browse

Help

Fail Replace Append

ERASE

This dialog can be used generate a #ERASE, #COPY, #RENAMEor #MOVE statement in your script. Refer to page 142 forinformation on that statement.

End Use this button to terminate the generation of your script. You willthen be asked for a file name for the script you have just created,then you will be returned to the main program window describedabove. The script file generated in response to the preceding threebuttons will be placed into the text box in the main window.

NOTE: the script file is not automatically saved for you. You mustuse the “Save” option from the File pulldown to write the scriptyou have just created to the PC disk.

If you attempt to exit the program without saving your script, adialog box will be displayed asking if you want to save the scriptfirst, or just exit the program.

If the script you have just generated is a HOSTAFT Script, you willneed to upload it to the host before it can be used. You can select“Upload Script to Host” from the File pulldown to begin the scriptupload process.

Cancel This terminates the script process. No information will be saved.



When you select one of the script building options (Signon, Download, orUpload) you will be presented with the same dialogs that are present in themanual transfer program, BIMFTR. As the script is generated, BIMAFT will issuethe associated query and signon commands to the mainframe and analyze thehost response.

For instance, the Signon process will actually sign on to the mainframecomponent of BIM-PC/TRANSFER. This way your user id and password will bevalidated as the script is built. The password you enter for the signon will beplaced into the script in encrypted form in an attempt to preserve passwordsecurity. Additionally, any access considerations for the user-id/passwordcombination will be fully taken into account as you build the script.

Likewise, the Download process will actually query the host for the file you haveselected. If the file is found, the necessary #DOWNLOAD and #TRANSFERstatements (see below) will be inserted into the script. If the file is not found, youwill be asked if you wish to add this entry into the script anyway. This latter caseis likely if you are generating a script for use overnight and the desired file is notcurrently available. You do not have to be at work at 3:00 A.M. in order toestablish a script to transfer files that aren't available until then (say thank you).

Using the Script File Recorder is the easiest way to generate an AutomaticTransfer Script.



Signon Dialog

When you select the “Signon” button on the “Script File Recorder” dialog, orselect “Save Signon to File” from the “File” menu, the following dialog will bedisplayed:

Sign on to File Transfer System

User Password File Name

Exit SettingsOK Help

Browse

This dialog is used to enter the options necessary to either; (1) generate a signonfile for use by a #SIGNON statement, or (2) generate a #SIGNON statement inyour script.

Generating a Signon File

UserPassword

These fields provide your user id and password, as defined to the hostBIM-PC/TRANSFER system. This information is required to determinewhat types of transfers you are authorized to perform.

File Name

This field is used to specify the name for the signon file on yourworkstation. The “Browse” button can be used to display a standard Filedialog to locate the directory for your file.

Generating a #SIGNON Statement

UserPassword

These fields provide your user id and password, as defined to the hostBIM-PC/TRANSFER system. This information is required to determinewhat types of transfers you are authorized to perform. These fields areignored if you use the File Name field.

File Name

This field is used to access a previously created signon file on yourworkstation that contains your user id and password. The “Browse”button can be used to display a standard File dialog to locate the name of



your file. If this field is used, the “User” and “Password” fields areignored

It is recommended that you use this method of user identification forHOSTAFT Scripts. That way, your userid and password are not stored inthe scripts on the host.

Note on Passwords

The #SIGNON statement and signon file generated by BIM-PC/TRANSFER willcontain the password in an encrypted format to protect from unauthorized useby others.

Execute PC Program Dialog

When you select the “Exec” button on the “Script File Recorder” dialog, thefollowing dialog will be displayed:

Execute:

Command Line:

Execute PC Program

OK Cancel

Browse

Help

Variable Substitution

%FNM - File Name, %PTH - Path, %PNM - Full Path and Name

This dialog is used to enter the options necessary to generate a #EXEC statementin your script. The following options are available:

Execute:

This is the name of the PC program to be executed. This must be the fullpath and name. If you do not know the complete name, press the“Browse” button, and a File Dialog will be displayed to allow you tosearch for the desired program name.

Command Line:

If the PC program to be executed requires command line options, enterthem here.


If this options is checked, the Command Line can contain variables thatwill be substituted when the script is executed. Refer to the section“#EXEC” on page 141 for more information on the use of these variables.



Automatic Transfer Options Dialog

When you select the “Option” button on the “Script File Recorder” dialog, thefollowing dialog will be displayed:

Transfer Log File Name

Pause time (in minutes)

Retry Count

1

Stop time (HH:MM 24 hr Clock):

Automatic Transfer Options

OK Cancel Help

Reload Script RELOAD=WAIT

Loop until Complete

BIMAFT.LOG

Script Options

Transfer Log Options

Load Script at End

Start time (HH:MM 24 hr Clock):

Yes No Print File

Quit On Completion

Yes No Warn

This dialog is used to enter the options necessary to generate a #OPTIONstatement in your script. Refer to page 130 for a description of these fields.



Host Transfer Send to Netname Dialog

When you select the “Sendto” button on the “Script File Recorder” dialog, thefollowing dialog will be displayed:

(Host Transfer) Send to Netname

OK Cancel Help

Keep HOSTAFT Status Record

Destination Netname(s)

This dialog is used to enter the values necessary to generate a #KEEP and/or a#SENDTO statement in your HOSTAFT Script. The following options areavailable:

Keep HOSTAFT Status Record

If this field is checked, a #KEEP statement is generated in yourHOSTAFT Script. The #KEEP statement instructs the host to keep thetransfer status record after completing the processing for this script. Ifthis option is not selected, the status records are deleted if no errors areencountered during processing. Status records can be reviewed anddeleted using the FTRM transaction.

Destination Netname(s)

Enter the VTAM netname of each PC workstation that is to receive thisHOSTAFT Script when it has been activated on the host. These entriesresult in one or more #SENDTO statements being generated in yourscript. If you need to specify more than sixteen PC’s, you can select thisdialog multiple times. A single HOSTAFT Script can contain a maximumof 128 PC netnames.



Automatic Transfer Script

The Automatic Transfer Script is comprised of the following statements:

Command Description Page* Comment. 126#COPY Copy a PC dataset. 142#DEFINENAME Define PC filename from host data. 148#DOWNLOAD Looks for a host file for download. 135#END Terminates the script. 154#ENDIF Terminate IFEXISTS/IFNOTEXISTS. 133#ERASE Erase/Delete a PC dataset. 142#EXEC Execute a PC program. 141#GOTO Conditional processing test. 153#HOSTAFT Activate Host Transfer 143#IF Conditional processing test. 152#IFEXISTS Check for file presence. 133#IFNOTEXISTS Check for file absence. 133#KEEP HOSTAFT Processing Option 127#MOVE Move a PC dataset. 142#OPTION Establishes run time options. 130#PROMPT User Prompt for processing options. 146#RENAME Rename a PC dataset. 142#SENDTO HOSTAFT Processing Option 128#SIGNON Sign on to the File Transfer System. 129#START Start a host transaction 144#TRANSFER Causes the selected file to be transferred, in

either an upload or a download direction.139

#UPLOAD Looks for a file on the PC for upload. 137@name Destination for #GOTO and #IF. 151

While it is certainly easier to let the program generate the script, you may wish tomanually change one or more entries once the script exists. The individual scriptstatements are described in more detail below.



Notes on Syntax:

Comments Comments are identified by an asterisk ('*') in the firstposition of the line.

Continuation Any script statement except the #SENDTO used inHOSTAFT scripts, may be continued by using the '-' as thelast non-blank in the line. The script input routine willappend the following line as a part of the continued scriptstatement. For example:

#OPTION LOOP=YES RETRY=99

and

#OPTION LOOP=YES -RETRY=99

will be treated the same by the input routine.

Character Data Character fields may be needed to select a file from the host,or to properly define an uploaded file to the host. If thesecharacter fields contain imbedded commas, then you mustenclose the character data within single quote marks. Forexample:

'Yogi, and Booboo'

Case The script processor is case insensitive, that is you do notneed to enter statements as upper case alphabetic. The scriptprocessor will consider “#OptIoN” to be equivalent to“#OPTION.”

HOSTAFT Script Syntax:

Scripts used for HOSTAFT processing have the following restrictions:

1) Each line of the script must be no longer than 72 characters.

2) The scripts are limited in length to 400 lines.



#KEEP

This statement can only be used in HOSTAFT Scripts.

#KEEP

#KEEP tells the host to keep the HOSTAFT Status record on the Host Control Fileafter the processing has completed. If this statement is not included, the statusrecord will be automatically deleted if all processing is completed OK. Thisstatement must be specified prior to the first #SENDTO, and must begin inposition 1 of the script line.

Refer to section “HOSTAFT Script Overview” on page 160 for more informationon the use of this statement.



#SENDTO

This statement can only be used in HOSTAFT Scripts.

#SENDTO netname1 netname2 netname3 netname4

The #SENDTO statement is a list of VTAM network names of the PC’s that are toprocess the script. You can include as many of these statements as you need, upto a maximum of 128 network names. The statement must begin in position 1 ofthe script line. The network names in the list can be separated by either spaces orcommas.

This statement must be physically positioned in the script prior to the scriptstatements that are to be sent to the PC workstation for processing.



#SIGNON

Just as in the manual transfer, you must issue a signon to the host component ofthe File Transfer System in order to move files from and/or to the PC. There aretwo formats for this statement, one containing your actual user id and password,and the second containing the name of a file on your PC workstation containingyour user id and password.

#SIGNON user password -or-#SIGNON FILE=PC.file.name

user

Your unique user id. This must match the user id you enteredwhen customizing the host system using the FTRM transaction.

password

The password associated with the user id above. This mustmatch the password entered when customizing the host systemusing the FTRM transaction.

If you make the script yourself, then you will need to enter thepassword as you would key it in at the signon prompt.

If you used the “RECORD” feature of the Automatic FileTransfer program to generate the script, the password providedon the #SIGNON statement is its encrypted form. This isidentified by enclosing the encrypted password within brackets“[...].” If you know the encrypted form of your password, youcan specify it enclosed in brackets as well.

FILE=PC.file.name

This format of the #SIGNON statement can be used to referencea signon file containing your userid and password. The signonfile is generated by selecting “Save Signon to File” from the“File” menu of program BIMAFT. Refer to page 121 for moreinformation.

You can have multiple signons within a single script. This may become necessaryif different files you wish to move have different levels of security authorization.The #DOWNLOAD and #UPLOAD statements will use the most recentlyencountered #SIGNON for their processing.

Example

#SIGNON DAVE FARGO



#OPTION

The #OPTION statement establishes run time parameters for this execution ofAutomatic File Transfer. The options are set globally and affect all transferattempts in the script. If more than one #OPTION statement is present in thescript, the last one encountered will be used at run time.

#OPTION LOG=NO|PRINT|file.name - LOADNEXT=fully.qualified.file.name - LOGON=pc.file.name.of.logon.script - LOGOFF=pc.file.name.of.logoff.script - LOOP=YES|NO - PAUSE=n - PROFILE=name - QUIT[=WARN] - RELOAD|RELOAD=WAIT|RELOAD=PROMPT - RETRY=nnn - START=hh(:mm) - STOP=hh(:mm)

The parameters are:

LOG=NO|PRINT|file.name

This option specifies overrides to the generation of the TransferLog. If this operand is omitted, the Transfer Log is maintained inmemory, for on-line viewing, and is not saved when theAutomatic Transfer Program terminates.

NO This will suppress the Transfer Log.

PRINT This will cause the Transfer Log to be printed on thePC’s attached printer when the entire script has beenprocessed.

file.name This will cause the Transfer Log to be written to thenamed PC file.

LOADNEXT=fully.qualified.file.name

If this option is specified, it provides the name of another BIM-PC/TRANSFER script file to be executed after the completion ofthe current script.

LOGON=pc.file.name.of.logon.script

Specifies the name of an optional Logon Script for use when aLU2/3270 connection is being used to communicate to the host.If this operand is specified, it overrides any value defined in the"LU2 Settings" dialog. Refer to "Example Automatic TransferScripts" on page 73 and "Logon/Logoff Scripts" on page 69 formore information.



LOGOFF=pc.file.name.of.logoff.script

Specifies the name of an optional Logoff Script for use when aLU2/3270 connection is being used to communicate to the host.If this operand is specified, it overrides any value defined in the"LU2 Settings" dialog. Refer to "Example Automatic TransferScripts" on page 73 and "Logon/Logoff Scripts" on page 69 formore information.

LOOP=YES|NO

If you specify YES (the default) Automatic File Transfer willcontinue processing until:• All transfer requests have been satisfied, either successfully

or by exceeding the RETRY count (see below),• Or, you cancel the process, whichever comes first.

If you specify NO, Automatic File Transfer will process the scriptone time only.

For overnight processing, you should specify LOOP=YES, or letit default. That way, when the host file is ready it will betransferred, and you are not dependent on the host schedule tohave your file ready at a specific time.

PAUSE=nnn

Use this to specify the number of minutes the PC should waitbetween attempts to satisfy the transfer requests containedwithin the script. The default is one minute and should beacceptable for most processing environments.

PROFILE=name

This option can be used if your PC has been configured for"Connection Profiles". This operand provides the 8-charactername of the profile to be used for this script. Refer tosection"Using Connection Profiles In Automatic Transfers" onpage 46 for more information.

QUIT|QUIT=WARN

These options will cause the Automatic Transfer Program toterminate processing once the entire script has been processed.Use QUIT=WARN to obtain a warning message if one or moreerrors are detected during script processing. If you use the QUIToption, the Automatic Transfer Program will terminateregardless of any errors in script processing.

RELOAD|RELOAD=WAIT|RELOAD=PROMPT

Either of these options will cause the script to be re-loaded andre-started after all specified transfers have been completed.

RELOAD causes the script to resume immediately.



RELOAD=WAIT causes a wait for the PAUSE interval beforeresuming. If the START operand has also been specified, thescript will resume at the specified START time.

RELOAD=PROMPT causes any #PROMPT statements to beredisplayed on the PC.

This option is intended for weekend (holiday) operations whereyou want the automated transfer to occur over a period ofseveral days without interruption, or if several items are to bedownloaded that have the same selection criteria.

RETRY=nnn

If you do not specify this operand, Automatic File Transfer willcontinue to retry your transfer request for ever. Generally, this isprobably correct. If, however, you wish to give up after a certainnumber of attempts, specify the number of attempts here.

START=hh(:mm)

Use this operand to specify a time of day (night) when the PC isto start the script process. For instance, your host file(s) may notbe available until 1:30 AM at the earliest. SpecifyingSTART=01:30 will avoid the overhead associated with queryingthe host until a time when the file(s) can be expected to beavailable. If omitted, Automatic File Transfer begins the scriptprocess immediately.

STOP=hh(:mm)

Use this operand to specify a time of day (night) when the PC isto stop the script process. If the PC program is left running afterscript processing has been stopped, and RELOAD has beenspecified, script processing will resume when the next STARTtime has been reached.



#IFEXISTS#IFNOTEXISTS#ENDIF

These statements are used to create a group of transfers to be performed basedon the existence or absence of a specific file.

The #IFEXISTS statement instructs Automatic File Transfer to determine if aspecific file is present. If it is, the statements following the #IFEXISTS will beexecuted in sequence. If the file is not present, processing will continue followingthe next #ENDIF statement.

The file can be either a PC file or a host file.

The #IFNOTEXISTS statement is the opposite of the #IFEXISTS statement. Thisstatement instructs Automatic File Transfer to execute the statements followingthe #IFNOTEXISTS only if the specified file does not exist.

#IFEXISTS PC.file.name#IFEXISTS category libque selection.criteria

#IFNOTEXISTS PC.file.name#IFNOTEXISTS category libque selection.criteria

#ENDIF

PC.file.name

For a PC file, include the full path and filename.

Example: C:\USER\FILE.DAT

category

This is the category name you have supplied during hostcustomization using the FTRM transaction. For example, at BIMwe use “POWER” for access to the VSE POWER queues.

libque

This is the LIBQUE that is associated with the category specifiedabove. Refer to page 196 for a table of valid libque values.

selection.criteria

Each category has a different set of selection criteria that is usedhere. Selection.criteria are comprised of a 1-3 character keyword,followed by an equal sign, followed by the selection data. Most



likely you will need more than one field to identify the file.Individual fields are separated by commas.

Selection criteria keywords are documented in the section“Driver Specifications” on page 306.

Examples

#SIGNON DDW [password]#IFEXISTS POWER LST JNM=BIMLNK99,CLS=L,DSP=* #DOWNLOAD VSAM ESDS #TRANSFER REPLACE#ENDIF#END

In the above example, the download of the VSAM dataset defined in profileESDS will only be performed if a POWER LST queue job BIMLNK99 can befound. The indentation of the #DOWNLOAD and #TRANSFER was done forclarity in the example, it is not required.

#SIGNON DDW [password]#IFEXISTS JES Held JNM=BIMLNK99,CLS=L #DOWNLOAD VSAM ESDS #TRANSFER REPLACE#ENDIF#END

In the above example, the download of the VSAM dataset defined in profileESDS will only be performed if a JES Held queue job BIMLNK99 can be found.The indentation of the #DOWNLOAD and #TRANSFER was done for clarity inthe example, it is not required.



#DOWNLOAD

The #DOWNLOAD statement instructs Automatic File Transfer to query the hostto see if a specific file is ready for transfer to the PC. The #DOWNLOADstatement must be immediately followed by a #TRANSFER statement (seebelow). If the file is found on the host, then the following #TRANSFER statementwill cause the file to be moved to the PC. If the file is not found on the host, thefollowing #TRANSFER statement will be bypassed.

Once a transfer is competed, the #DOWNLOAD/#TRANSFER pair of statementswill be removed from Automatic File Transfer's internal tables. A #DOWNLOADstatement will move one file and one file only. If you have multiple files to move,you will need multiple #DOWNLOAD statements in your script.

#DOWNLOAD category libque [GENERIC] selection.criteria

There are four pieces of information you need to supply on the #DOWNLOADstatement:

category

This is the category name you have supplied during hostcustomization using the FTRM transaction. For example, at BIMwe use “POWER” for access to the VSE POWER queues. Youmust supply the category.

libque

This is the LIBQUE that is associated with the category specifiedabove. You must supply the LIBQUE. Refer to page 196 for atable of valid libque values.

GENERIC

This is an optional operand. If specified, it must be specifiedbetween the libque and the selection.criteria. It states that theselection.criteria specifies a generic selection, and all matchingitems on the host are to be downloaded to the PC.

If the “download.file.name” on the #TRANSFER statement isspecified as “*.*” or “*.sfx”, then each matching host file will betransferred into a separate PC file, otherwise they will all becombined into a single PC file.

If this operand is omitted, and the selection.criteria is generic,only the first host file that matches the criteria will betransferred.



selection.criteria

Each category has a different set of selection criteria that is usedhere. Selection.criteria are comprised of a 1-3 character keyword,followed by an equal sign, followed by the selection data. Mostlikely you will need more than one field to identify the file.Individual fields are separated by commas.

Selection criteria keywords are documented in the section“Driver Specifications” on page 306.

Examples

Here, we are looking for a report in the POWER LST queue, class B, namedBIMFTRIT. The #DOWNLOAD statement looks like:

#DOWNLOAD POWER LST CLS=B,JNM=BIMFTRIT

Here, we are looking for a report in the JES Output queue, class B, namedBIMFTRIT. The #DOWNLOAD statement looks like:

#DOWNLOAD JES Output CLS=B,JNM=BIMFTRIT



#UPLOAD

The #UPLOAD statement instructs Automatic File Transfer to attempt to locatethe PC file specified in the statement. The #UPLOAD statement must beimmediately followed by a #TRANSFER statement (see below). If the file isfound on the PC, then the following #TRANSFER statement will cause the file tobe moved to the host. If the file is not found on the PC, the following#TRANSFER statement will be bypassed.

Once a transfer is completed, the #UPLOAD/#TRANSFER pair of statementswill be removed from Automatic File Transfer's internal tables. A #UPLOADstatement will move one file and one file only. If you have multiple files to move,you will need multiple #UPLOAD statements in your script.

#UPLOAD category libque PC.file.name [SCRIPT] [UNIQUE] host.name

There are several pieces of information you need to supply on the #UPLOADstatement:

category

This is the category name you have supplied during hostcustomization using the FTRM transaction. For example, at BIMwe use “POWER” for access to the VSE POWER queues. Youmust supply the category.

libque

This is the LIBQUE that is associated with the category specifiedabove. You must supply the LIBQUE. Refer to page 196 for atable of valid libque values.

PC.file.name

This is the name of the file you want to move to the host. It canbe:

• A full PC filename including drive and path.• A generic PC filename mask if more than one PC file isto be selected. See the UNIQUE option below for moreinformation.

SCRIPT

This is an optional operand. If specified, it indicates that thePC.file.name is a “File Upload Script”. Refer to page 174 forinformation on file upload scripts.

UNIQUE

This is an optional operand. It only applies to uploads thatspecify a generic PC.file.name. If UNIQUE is specified, all



matching PC files will be transferred to the host as unique filesusing the PC file name and extension to identify the files on thehost. If UNIQUE is not specified, all matching PC files will betransferred to the host as a single host file. See host.name belowfor options on controlling the names of the host files.

host.name

Each category has a different set of fields that are used toproperly name a file on the host system. These fields arecomprised of a 1-3 character keyword, followed by an equal sign,followed by the field data. Most likely you will need more thanone field to identify the file. Individual fields are separated bycommas.

Keywords are documented in the section “Driver Specifications”on page 306.

If you are uploading several files using a generic PC.file.name,and have included the UNIQUE option, you can control thegeneration of the host.name field contents by use of severalsubstitution variables. Refer to section “Generic Uploads Usingthe Unique Option” on page 103 for more information.

Examples

Here, we are transferring file C:\BINGO\UPIT.TXT to the POWER LST queue,class B, named BIMFTRED. We will add some descriptive text to the POWERUSER field. The #UPLOAD statement looks like:

#UPLOAD POWER LST C:\BINGO\UPIT.TXT CLS=B, - JNM=BIMFTRED, - USR='FROM PC'

Here, we are transferring file C:\BINGO\UPIT.JCL to the JES Internal Reader,.The #UPLOAD statement looks like:

#UPLOAD JES IRDR C:\BINGO\UPIT.JCL

In this example, we are transferring all entries in directory D:\PATH with anextension of “DAT” to the POWER LST queue. Each entry in the queue will havethe name of the PC file, and be in class “L”:

#UPLOAD POWER LST D:\PATH\*.DAT UNIQUE JNM=*,CLS=L

In the above example, JNM=* could also be specified as JNM=%SNM.



#TRANSFER

The #TRANSFER statement causes a file to be moved. The direction (upload ordownload) and the file name are determined from the preceding #DOWNLOADor #UPLOAD statement.

#TRANSFER ASCII|NOASCII - CRLF|NOCRLF - NODELETE - REPLACE|RENAME|CANCEL|APPEND|NEW - download.file.name

The operands are:

ASCII|NOASCII

For most #TRANSFER operations this operand is not needed. Ifyou have a special case where you cannot except the defaultASCII translation options contained within the mainframe driverprogram, then you can override the default action here. If thedefault is sufficient for your purpose, do not include eitherASCII or NOASCII on the #TRANSFER statement.

CRLF|NOCRLF

For most #TRANSFER operations this operand is not required. Ifyou have a special case where you cannot except the defaultCR/LF processing contained within the mainframe driverprogram, then you can override the default action here. If thedefault is sufficient for your purpose, do not include either CRLFor NOCRLF on the #TRANSFER statement.

NODELETE

This operand can be used when downloading reports from aPOWER queue. It prevents the #DOWNLOAD-#TRANSFERpair from being deleted upon successful data transfer.

This operand is useful in situations where there are multiplePOWER reports with the same selection criteria, and you want totransfer them all with a single script definition.

It should be used in conjunction with the RENAME or APPENDoperands to avoid data loss.

You must also use the ALTER or DELETE driver options fordriver BIMFTRDP, or you will merely transfer the same reportover and over again.

When using the NODELETE operand, the script will not quit.Instead, the #DOWNLOAD will be retried for ever. One way to



cause the script to stop is to specify the OPTION RETRY operandwith a value to limit the number of attempts for the transferbefore automatically stopping.

REPLACE|RENAME|CANCEL|APPEND|NEW

This operand defines how duplicate file names will be handledduring the file transfer process. The usage varies according to thedirection of transfer (upload or download) and by the individualcategory specified in the preceding #DOWNLOAD or#UPLOAD statement.

For downloads, REPLACE, RENAME, APPEND, and CANCELcan be used. The default for a download transfer is REPLACE. Ifyou specify CANCEL and a identically named file exists on thePC, the transfer operation will not be retried.

For uploads, REPLACE, APPEND and NEW can be useddepending on the category specified in the preceding #UPLOADstatement. These options are not always available for allcategories. Consult driver details for more information.

download.file.name

This operand is only relevant to a download process. It is used tospecify a destination name for the downloaded file. You mustspecify the full path name for the file, e.g.C:\BONGO\GRABED.TXT. If omitted, the downloaded file willbe placed in the working directory for the Automatic FileTransfer program and will be named based on the mainframefile.

A special format of the filename has been provided fordownloads. If you specify the PC filename as “*.*”, the currenthost filename will be used. You can also specify the PC filenameas “*.sfx” where sfx is the suffix to be used for all filestransferred.



#EXEC

The #EXEC statement signals Automatic File Transfer to execute a PC programwhile processing the script. This statement is not supported in the DOS(BIMAFTD) version. The OS/2 (BIMAFTO) version can only execute programswritten for OS/2. The Microsoft Windows (BIMAFT) version can executeprograms written for windows or DOS.

#EXEC statements will not be processed if the immediately preceding transferfails to complete. #EXEC statements located prior to the first transfer in the scriptwill always be processed.

#EXEC [NOSUB] program.name [command.line.options]

NOSUB

This optional operand specifies that no variable substitution is tobe performed against the “command.line.options”.

program.name

This operand specifies the complete path name of the program tobe executed.

command.line.options

Everything after the program.name is considered to be commandline options to be passed to the program. Limited variablesubstitution is available within the command line options. Threevariables can be used:

%FNM Name of the most recently transferred file.%PNM Name, including path, of the most recently transferred

file.%PTH Path only of the most recently transferred file.

For example, if immediately preceding the #EXEC statement youdownloaded into:

C:\BIMWIN\FTR\DATAFILE.DAT

the three variables would be expanded as follows:

%FNM DATAFILE.DAT%PNM C:\BIMWIN\FTR\DATAFILE.DAT%PTH C:\BIMWIN\FTR



#COPY#RENAME#MOVE#ERASE

These statements signal Automatic File Transfer to perform the designatedfunction while processing the script.

These statements will not be processed if the immediately preceding#TRANSFER fails to complete. If one or more of these statements are locatedprior to the first #TRANSFER in the script, they will always be processed.

#COPY from.name to.name [REPLACE|APPEND]#RENAME from.name to.name [REPLACE]#MOVE from.name to.name [REPLACE]#ERASE from.name

#RENAME and #MOVE are functionally equivalent.

from.name

This operand specifies the complete path name of the item to becopied, renamed, moved, or erased.

to.name

This operand specifies the complete new path name of the itemto be copied, renamed or moved.

REPLACE

The copy, rename and move will fail if the 'to.name' alreadyexists unless this operand is specified.

APPEND

Can be specified on the #COPY to cause the 'from.name' to beappended to the 'to.name'.



#HOSTAFT

The #HOSTAFT statement signals Automatic File Transfer to activate aHOSTAFT Script for processing. This statement will normally be used followingan upload of data that is to be then sent to one or more other PC workstations.

#HOSTAFT statements will not be processed if the immediately precedingtransfer fails to complete. #HOSTAFT statements located prior to the firsttransfer in the script will always be processed.

#HOSTAFT script,[jobname],[parm1],[parm2],[parm3], - [parm4],[parm5],[parm6],[parm7],[parm8]

script

This is the name of the HOSTAFT Script to be activated. If thescript name contains blanks, enclose this field in quotes.

The remaining operands are optional. They are, however, positional. That is, ifyou omit any of these fields, you must still include the commas that separatethem. You can only omit the commas that follow the last field you specify. Referto section “HOSTAFT Activate Script Screen” described on page 249 for adescription of these operands.



#START

The #START statement signals Automatic File Transfer to start a host transactionwhile processing the script.

#START statements will not be processed if the immediately preceding transferfails to complete. #START statements located prior to the first transfer in thescript will always be processed.

#START tran, -[TRM=netname|*, -][REQ="reqid", -][INT=hhmmss|TIM=hhmmss, -][DAT="start data"]

tran

This operand is required. It specifies the CICS or BIM-TMANtransaction id to be started on the host.

TRM=netname|*

This operand is optional. If omitted, the host transaction will bestarted as a non-terminal task. If specified, it must be either an"*" to indicate that the host transaction should be started on thecurrent PC terminal, or it must be the VTAM network name forthe terminal/PC on which the host transaction should be started.

TRM=* is not supported when your PC is connected to the hostvia an APPC connection.

INT=hhmmss|TIM=hhmmss

This operand is optional. One or the other of these formats canbe specified if you want to delay the start of the transaction onthe host. INT=hhmmss specifies an interval that is to be waitedbefore the transaction is started. TIM=hhmmss specifies theactual time when the transaction is to be started.

The host treats the TIM value as relative to the midnight prior tothe 'current time'. A TIM value will be considered expired if itprecedes the current time by up to six hours. If it precedes thecurrent time by more than six hours, the host will add 24 hoursto the TIM value specified.

REQ="reqid"

This operand is optional. It can be used to specify a CICS requestid (1 to 8 characters) for a TIM or INT start. This request id canbe used in CICS to cancel an outstanding start. If omitted, spacesis assumed.



DAT="start data"

This operand is optional. It can be used to specify up to 256characters of data to be passed to the host transaction as part ofthe start request.



#PROMPT

The #PROMPT statement can be used to request input from the PC user prior tostarting a script.

#PROMPT %fldname DEFAULT=default - LIST=(xxx,yyy,zzz,...) - HDG='heading text' - LENGTH=n

You can specify as many #PROMPT statements as required for your script, butthey must all appear at the beginning of your script.

If one or more #PROMPT commands are encountered, the PC user will bepresented with a dialog asking for choices as you have laid out in the#PROMPTs. The PC user may cancel the dialog in which case AutomaticTransfer processing will not continue. If the PC user presses OK, the #PROMPTresults will be substituted into the remainder of the script, and the resultingconverted script will be executed by the Automatic Transfer program.

If your script contains #OPTION RELOAD, the Automatic Transfer program willreload the converted script. The PC user will not be prompted a second time. Ifyou want the PC user to be prompted again, then you should use:

#OPTION RELOAD=PROMPT

This will cause the original, unaltered script to be reloaded and the PC user willsee the prompts again.

The #PROMPT statement can be continued to multiple script lines by specifyinga '-' as the last character of each line except the last line of the statement.

%fldname

Required. This is the field identifier that can appear in asubsequent #IF statement. 'fldname' can be any alphabeticcharacters, up to 8 in length. The '%' is required as the firstcharacter.

LENGTH=n

Required. This is the maximum length of the response by the PCuser.

DEFAULT=default

Provides the default to be used for %fldname if the PC user doesnot enter anything in response to this prompt. If this operand isomitted, the PC user must enter a value for this prompt.

Note: If a LIST operand is provided, and the DEFAULT operandis omitted, the 1st value in the LIST is used for the default.



LIST=(xxx,yyy,zzz,...)

Optional operand that provides a list of valid responses that canbe entered by the PC user. If the entered data can contain spaces,the individual values in the list must be specified within quotes.

HDG='heading text'

This text will be displayed as the prompt to the PC user. Up to 40characters can be specified.

Example:

#PROMPT %FLD1 HDG='Replace/Rename Option' - LENGTH=7 - LIST=(REPLACE,RENAME)

In this example, prompt field %FLD1 is defined as a 7 character field. The PCuser can respond with one of two choices: REPLACE or RENAME. The implieddefault is REPLACE.



#DEFINENAME

The #DEFINENAME statement can be used to construct the filename for a#TRANSFER command using data from the 'Available Items' line for the host filebeing transferred.

You must use the Record feature of Automatic Transfer to determine the fieldlayouts for individual Categories within BIM-PC/TRANSFER.

All scripts containing #DEFINENAME statements should be reviewed afterevery new release is installed of the host BIM-PC/TRANSFER software. Theoffset and lengths of fields may change from release to release.

#DEFINENAME %filename - FIELD=offset,length[,format] - LITERAL=xxxxx - LIBQUE=offset,length[,format] - CATEGORY=offset,length[,format] - SEPARATOR=x - EXT=xxx

Where:offset relative to zerolength length of data to moveformat TRUNC or NOTRUNC. TRUNC removes trailing spaces. The

default is NOTRUNC.

BIM-PC/TRANSFER constructs a name field using the specified fields andoperands in the order that the operands are specified in the command. You canuse any combination of operands.

%filename

Required. This is the field identifier that can appear in asubsequent #TRANSFER statement as all or part of the'download.file.name' field. 'filename' can be any characters, up to8 in length. The '%' is required as the first character.

FIELD

Refers to a field in the heading string returned from themainframe for this Category/Libque combination. Thisinformation can be extracted from BIM-PC/TRANSFER throughthe Record feature by selecting the Define Name process.

LITERAL

Inserts a literal. If the data contains imbedded spaces, then itmust be enclosed within either single or double quotes ( ‘ or “ ).NOTE: The keyword “LITERAL=” is not strictly necessary. Ifthe Automatic Transfer program can’t recognize the word, itassumes it is a literal.



LIBQUE

This is the libque for the download. By default, the valueinserted will be the length of the libque entry which can varydepending on the Category selected. You can optionally applyoffset and length values to change the field length. If the length isgreater than the actual data found during execution, the fieldwill be left justified and padded with spaces.

CATEGORY

This is the Category of the current download. By default, thevalue inserted will be the length of the Category entry. You canoptionally apply offset and length values to change the fieldlength. If the length is greater than the actual data found duringexecution, the field will be left justified and padded with spaces.

SEPARATOR

You can optionally specify a separator to be inserted between thevarious entries. The separator is one byte in length.

EXT

You can use this operand to specify the three-character extensionfor the file name. Use of this option is functionally equivalent tocoding a literal value. That is, the two statements:EXT=TXTLITERAL=.TXT

will produce the same results.

Example:

Use of Automatic Transfer record feature for a Category defined for BIM-EDITwill result in a #DEFINENAME entry being added to the generated script whichlooks like:

#DEFINENAME EDIT /* BIM-EDIT Library Access */ - FIELD=0,16 /* Member */ - FIELD=17,8 /* Type */ - FIELD=26,40 /* Title */ - FIELD=67,6 /* Lines */ - FIELD=74,8 /* Attr */ - FIELD=83,10 /* Create Dte */ - FIELD=94,10 /* Update Dte */ - /* End of Definition for Category =EDIT */

The following sample script uses a modified version of the above#DEFINENAME statement to construct PC file names using the BIM-EDITmember name, title and type fields. A dash is inserted between the membername and title, and the PC file extension used the BIM-EDIT type field:



#SIGNON . . .#DEFINENAME %EDIT /* BIM-EDIT Library Access */ - FIELD=0,16,TRUNC /* Member */ - '-' - FIELD=26,40,TRUNC /* Title */ - '.' - FIELD=17,3,TRUNC /* Type */#DOWNLOAD EDIT DDW GENERIC MEM=BIMD*,#TRANSFER REPLACE E:\TEST\%edit#END



Labels

The #IF statement (below) may cause processing to skip around within the Script.The Label statement defines the location for processing to continue whenever a#IF statement is evaluated as true.

@name

name

Is your choice and can contain up to 30 characters. The label maynot contain imbedded spaces. The label search is case sensitive,that is “A” is not the same as “a.”

Example:

@HAPPYHOUR



#IF

The #IF statement allows you to jump around within the Script.

#IF field condition comparand label

field

Is the %fldname from a #PROMPT statement.

condition

Can be one of the following six options:

= Equal to,<> Not equal to,> Greater than,>= Greater than or equal to,< Less than, or<= Less than or equal to.

comparand

This is either a literal or a %fldname from a #PROMPTstatement. It will be compared to the field above. Literals thatcontain embedded spaces must be enclosed within single quotes.

label

This is the label name where processing will resume if thecomparison specified in the #IF statement evaluates to true. Ifthe comparison evaluates to false, the next sequential statementin the Script will be processed.

The label can be located either before or after the #IF statement.

Example:

#IF %FLD1 = REPLACE doreplace • • •@doreplace • • •



#GOTO

The GOTO causes processing to continue at a different point in the script.

#GOTO label

label

This is the label name where processing will resume.

The label can be located either before or after the #GOTOstatement.



#END

The #END statement signals Automatic File Transfer to stop processing scriptinformation. It must be the last line of the script. It will be the last executed line ofthe script.

#END



Sample Scripts

1. A little bit of everything

* Sample Automatic Transfer Script

(A) #OPTION START=02:45

(B) #SIGNON DAVE FARGO*

(C) #DOWNLOAD POWER LST CLS=B,JNM=BIMQCAT#TRANSFER RENAME C:\BIM\QCAT*

(D) #UPLOAD POWER LST C:\BIM\DOUP.TXT CLS=B, - JNM=BIMUPED, - USER='FROM DAVE'#TRANSFER NOASCII NOCRLF 80*

(E) #END

where:

(A) Processing will not begin until 2:45 a.m.

(B) Signon is required.

(C) Automatic Transfer will look for job BIMQCAT in the POWER LST queue,class B. If found, this report will be transferred to the PC into directory\BIM and named QCAT. If identically named files exist, the new file willbe renamed.

(D) Automatic Transfer will move the PC file named DOUP.TXT in directory\BIM to the POWER LST queue. This transfer will be accomplishedwithout ASCII translation (data on PC is assumed to be in EBCDICalready) and without carriage return/line feed processing. The assumedline length will be 80 bytes.

(E) End of script processing.



2. A series of downloads


(A) #SIGNON DAVE FARGO*

(B) #DOWNLOAD POWER LST CLS=B,JNM=BIMXFR1#TRANSFER C:\BIM\BIMXFR1.TXT*

(C) #DOWNLOAD POWER LST CLS=B,JNM=BIMXFR2#TRANSFER RENAME C:\BIM\XFR2\BIMXFR2*

(D) #DOWNLOAD VSAM BIMXFIL#TRANSFER C:\BIM\VSAM\XFIL*

(E) #END

where:

(A) Signon is required.

(B) When job BIMXFR1 is found in the POWER LST queue, it will betransferred to the PC, replacing an existing file if present.

(C) When job BIMXFR2 is found in the POWER LST queue, it will betransferred to the PC. If a duplicate file name exists on the PC, the newlytransferred data will be renamed.

(D) The VSAM file identified by profile BIMXFIL will be transferred to the PCreplacing an existing file if present.

(E) End of script processing.



3. A Sample Using #PROMPT


(A) #PROMPT %fnam DEFAULT=PCFILE - HDG=’PC File Name’ - LENGTH=12

(B) #PROMPT %rpls DEFAULT=REPLACE - HDG=’Replace/Rename Option’ - LIST=(REPLACE, RENAME) - LENGTH=14#SIGNON user password#DOWNLOAD POWER LST JNM=power.job,CLS=L

(C) #TRANSFER %rpls D:\BIMPCTFR\%fnam#END

where:

(A) This #PROMPT is used to ask the PC user for the destination file name onthe PC.

(B) This #PROMPT is used to ask the PC user whether the destination filename on the PC should be replaced or renamed.

(C) The results of the two #PROMPT statements will be inserted into this line.



4. A Sample Using #PROMPT, #IF and #GOTO

* Sample Automatic Transfer Script#PROMPT %WHI DEFAULT=SHORT - LENGTH=5 - HDG='Which One?' LIST=(SHORT,LONG,BOTH)#SIGNON DDW DDW#IF %WHI = SHORT DOS#IF %WHI = BOTH DOBOTH*@DOLONG*#DOWNLOAD POWER LST JNM=BIMPRT01,CLS=L,DSP=*,#TRANSFER REPLACE D:\BIMWIN\FTR0\AUTO\BIMLNKQC#END*@DOS*#DOWNLOAD POWER LST JNM=BIM32E62,CLS=L,DSP=*,#TRANSFER REPLACE D:\BIMWIN\FTR0\AUTO\BIMLNKQC#END*@DOBOTH*#DOWNLOAD POWER LST JNM=BIM32E62,CLS=L,DSP=*,#TRANSFER REPLACE D:\BIMWIN\FTR0\AUTO\BIMLNKQC#GOTO DOLONG#END

This example illustrates the use of #IF, #GOTO and @label commands todynamically construct a scripted process depending on user input. In this casethe script processing does not replace data in the script, but instead, #PROMPTinput is used to determine which piece(s) of the script will be used. Note that theconversion process will stop when it encounters a #END command.


Host Initiated Automatic File Transfer (HOSTAFT) Page 159

Host Initiated Automatic File Transfer (HOSTAFT)The HOSTAFT feature of BIM-PC/TRANSFER provides the support mechanismto allow transfers of data to occur between PC workstations and a host systemthat are initiated by either a host batch job stream or a CICS application program.

This feature is an extension of the basic Automatic File Transfer feature of BIM-PC/TRANSFER that is described starting on page 107. You should be familiarwith, and have used that feature before attempting to use the HOSTAFT feature.

Overview

Unlike the basic Automatic File Transfer feature that utilizes scripts stored andrun on each PC workstation, the HOSTAFT feature uses scripts stored on thehost, but executed on the workstation.

These “HOSTAFT Scripts” are the same type of scripts that would have beenused by BIMAFT in basic mode, but these contain additional information thatinstruct the host on which PC workstations the script should run. The scripts canbe created directly on the host using the FTRM transaction, or they can be createdon the PC using BIMAFT, and then transferred to the host for future processing.Since these scripts will normally require many specific operands, you will find iteasier to generate them on the PC using the “record” feature of BIMAFT.

When a PC user wants to make their workstation eligible for HOSTAFTprocessing, they must start the PC Automatic Transfer Program (BIMAFT) ontheir workstation, and if needed, establish a connection between theirworkstation and the host. They must then place BIMAFT in “Host Mode”, whichcauses it to periodically query the host for any transfers that need to beperformed. This process is explained in more detail later in this section.

On the host side, when a set of transfers are ready to be performed, the requiredHOSTAFT script(s) are “activated” by one of the following methods:

• By use of a BIM-PC/TRANSFER batch job step included in a application jobstream. This is described in detail below.

• By a CICS application program linking to BIM-PC/TRANSFER with a specialCOMMAREA. This is also described in detail below.

• By use of the FTRM Host transaction. Refer to section “HOSTAFT ActivateScript Screen” on page 249 for more information.

• By a PC workstation running the BIMAFT program. Refer to dialog option“Activate Host Transfer” on page 114 for more information.

Once a HOSTAFT script has been “activated”, the host side of BIM-PC/TRANSFER will examine the script to determine which PC’s are to run the


Page 160 Host Initiated Automatic File Transfer (HOSTAFT)

script, and will generate a HOSTAFT status record in the Host Control file. Thestatus record can be viewed and maintained using the FTRM transaction. Thehost then waits for each PC in “Host Mode” to query it for work to be done.When the query is made, the script is transmitted to the PC, and the PC executesthe script just like any normal Automatic File Transfer Script.

When the PC workstation completes execution of a HOSTAFT script, it notifiesthe host, passing to the host any error log generated during the process. The hostthen updates the HOSTAFT status record with the PC’s completion status. ThePC workstation will then repeat the query process checking for additionalHOSTAFT scripts that are “activated” for its processing.

The host will transfer each “activated” script to each PC workstation in the orderin which the scripts were originally activated.

The remainder of this section will provide details of how the HOSTAFT processis implemented and used.

Monitoring HOSTAFT Status

Each time a HOSTAFT Script is activated, a status record is generated in the BIM-PC/TRANSFER Host Control File. These status records are updated each time anaction occurs by the host or a PC workstation. You can view and maintain theseentries using the host FTRM transaction.

When all processing for a HOSTAFT Script has been completed by all requiredPC workstations, if no errors were detected, the status record is deleted from theHost Control File. If you want to maintain this information for future reference,you can include the #KEEP statement in the script. This will prevent the statusrecords from being deleted until you delete them manually using the FTRMtransaction.

Refer to section “HOSTAFT Status List” on page 242 and section “HOSTAFTStatus Detail Screen” on page 244 for additional information.

HOSTAFT Script Overview

HOSTAFT Scripts are essentially Automatic File Transfer scripts with additionalstatements that tell the host which PC’s are to execute the script.

There are two script control statements unique to HOSTAFT, they are: #KEEPand #SENDTO.

#KEEP tells the host to keep the HOSTAFT Status record on the Host Control Fileafter the processing has completed. If this statement is not included, the statusrecord will be automatically deleted if all processing is completed OK. Thisstatement must be specified prior to the first #SENDTO, and must begin inposition 1 of the script line.

The #SENDTO statement is a list of VTAM network names of the PC’s that are toprocess the script. You can include as many of these statements as you need, upto a maximum of 128 network names. The statement must begin in position 1 of



the script line. The network names in the list can be separated by either spaces orcommas.

If you have a script that you need to send to more than one PC, you must takeinto consideration the PC directories involved, and the #SIGNON requirements.

The #SIGNON statement is required in all transfer scripts. You will probably notwant to include the userid and password of each PC user in your HOSTAFTscripts. The #SIGNON statement has the ability to access a dataset on the PC toobtain signon information. Refer to page 129 for more information.

If all of the PC’s are using the same directory and file names, you can use a scriptin the following format:

#KEEP#SENDTO PCLU01 PCLU02#SIGNON FILE=D:\FTR\USER.DAT#DOWNLOAD POWER LST JNM=JOBONE#TRANSFER RENAME D:\FTR\HOST\JOBONE#END

If all of the PC’s are using different directory and/or file names, you can use ascript in the following format:

#KEEP ( 1)#SENDTO PCLU01 ( 2)#SIGNON FILE=D:\FTR\USER1.DAT ( 3)#DOWNLOAD POWER LST JNM=JOBONE ( 4)#TRANSFER RENAME D:\FTR\HOST1\JOBONE ( 5)* ( 6)#SENDTO PCLU02 ( 7)#SIGNON FILE=D:\FTR\USER2.DAT ( 8)#DOWNLOAD POWER LST JNM=JOBONE ( 9)#TRANSFER RENAME D:\FTR\HOST2\JOBONE (10)#END (11)

Notice that there is only one #END statement, and it is at the end of the script. Inthis example, the PC workstation with netname PCLU01 will receive lines (3)-(6)of the script, and the PC with netname PCLU02 will receive lines (8)-(10). Thecomment line (6) is specified for clarity, it is not required.

Lines (2) and (7) can specify multiple netnames on the same line, or can be aseries of consecutive #SENDTO statements.

When the host examines the script and finds a PC’s netname in a #SENDTOstatement, it skips to the next line in the script that is not a #SENDTO, and thensends all script lines until it reaches another #SENDTO, or it reaches the end ofthe script.

The same PC netname can appear in multiple places in the same script. In thatcase, the PC will receive the portions of script following each #SENDTOcontaining its netname, as if it were a single script series, and will be executed bythe PC as a single Automatic file Transfer Script.



These examples only show a single transfer with no special processing options. Inyour scripts, you are free to use any and all of the statements allowed in anAutomatic File Transfer Script, and can include any number of transfers, bothuploads and downloads.

As was mentioned in the Overview above, you will find it the easier to generatethese scripts using the “record” feature of program BIMAFT. Refer to section“Script Recording” on page 117 for more information.

HOSTAFT Script Variable Substitution

BIM-PC/TRANSFER provides a series of "Variables" that you can use in yourHOSTAFT script that will be replaced with actual data at the time the script isactivated for processing.

System variables can be specified in any combination and at any location in thescript. The substitution occurs prior to any other processing of the script. Thefollowing table lists the variables and what they generate:

Variable name Description Length%JOBNAME Job name from HOSTAFT Command 0-8 char.%NETNAME VTAM netname of activating connection 1-8 char.%SCRIPT Current Script name 1-16 char.%UP1 UPARM from HOSTAFT/UPARM command 0-8 char.%UP2 UPARM from HOSTAFT/UPARM command 0-8 char.%UP3 UPARM from HOSTAFT/UPARM command 0-8 char.%UP4 UPARM from HOSTAFT/UPARM command 0-8 char.%UP5 UPARM from HOSTAFT/UPARM command 0-8 char.%UP6 UPARM from HOSTAFT/UPARM command 0-8 char.%UP7 UPARM from HOSTAFT/UPARM command 0-8 char.%UP8 UPARM from HOSTAFT/UPARM command 0-8 char.

Variable names must be specified in either ALL upper case or all lower case. If avariable is specified in a script, and no data is provided for it during activation,the substitution process removes the variable as if it had not been specified in thescript.

Activating/Deactivating HOSTAFT on The PC

To enable each PC workstation to receive HOSTAFT Scripts for processing, youmust activate the BIM-PC/TRANSFER Automatic Transfer program (BIMAFT)and place it into “Host Mode”.

Refer to page 107 for instructions on how to activate BIMAFT in the various PCenvironments.

Once program BIMAFT is active, you place it into “Host Mode” by selecting“Enter Host Mode” from the “File” menu. This will cause the BIMAFT windowto minimize, and begin querying the host for work to be performed. If the host



has a script for the workstation to execute, it sends the script in response to thequery. If the host does not have anything for the workstation to do, theworkstation will wait for a specified time interval, and then re-issue the hostquery. The interval between queries is set using the BIMAFT program option“Host Transfer Wait”. The default is to query once every minute. Thisquery/process/wait sequence will continue until you deactivate HOSTAFT onthe PC.

To deactivate HOSTAFT on the PC, double-click the minimized ICON forBIMAFT, and select “Exit” from the “File” menu.

Activating A HOSTAFT Script for Processing

When host processing has reached a point where transfers in a particularHOSTAFT Script can be performed, the script must be “activated” for execution.This can be performed using any of the following methods:

• By use of a BIM-PC/TRANSFER batch job step included in a application jobstream. This is described in detail below.

• By a CICS application program linking to BIM-PC/TRANSFER with a specialCOMMAREA. This is also described in detail below.

• By use of the FTRM Host transaction. Refer to section “HOSTAFT ActivateScript Screen” on page 249 for more information.

• By a PC workstation running the BIMAFT program. Refer to dialog option“Activate Host Transfer” on page 114 for more information.

The host side of BIM-PC/TRANSFER will examine the “activated” script todetermine which PC’s are to run the script, and will generate a HOSTAFT statusrecord in the Host Control file. The status record can be viewed and maintainedusing the FTRM transaction. (Refer to pages 242 and 244).

The host then waits for each PC workstation in “Host Mode” to query it for workto be done. When a query is made, the script is transmitted to the workstation,and the workstation executes the script just like any normal Automatic FileTransfer Script.

As each PC workstation completes its processing of the script, it notifies the host,and includes an error log if any problems were detected. The host then updatesthe status record for the HOSTAFT Script, and records any error log data.

If you need to terminate a HOSTAFT Script after it has been activated, use theFTRM transaction as described starting on page 244.

Activating A HOSTAFT Script In Batch

BIM/PC/TRANSFER includes a batch program (BIMFTRBC) which can be usedin a batch job stream, as either a complete job or as a single jobstep in anapplication job to activate HOSTAFT Scripts for processing.



Program BIMFTRBC establishes a VTAM APPC connection to the CICS or BIM-TMAN region/partition that is executing the host side of BIM-PC/TRANSFER.Before you can execute this program, you must provide VTAM and CICSdefinitions for the APPC connection. No definitions are required in BIM-TMAN.

VTAM Definitions for BIMFTRBC

BIMFTRBC requires a VTAM APPL definition for its use in establishing theAPPC connection. The following example can be used:

HOSTAFT1 APPL AUTH=(ACQ),PARSESS=YES,APPC=YES, X DLOGMOD=APPC,MODETAB=ATCMODE

The name “HOSTAFT1” can be any name you want. The DLOGMODE andMODETAB values can also be any name you want. If you do not currently have alogmode definition for APPC connections, refer to section “VTAM Definitions onthe Host for APPC” on page 59 for help in defining one.

You will need a separate VTAM APPL definition for each concurrent executionof BIMFTRBC. You can define a “pool” of definitions by ending the APPL namewith a number, such as “HOSTAFT1” or “HSTAFT01”, and creating a series ofconsecutively numbered definitions, such as HSTAFT01, HSTAFT02, HSTAFT03,etc. BIMFTRBC will search the pool looking for an available definition to use forthe APPC connection. Refer to section “OPTION Command” on page 167 forinformation on how to control the VTAM “pool” processing.

CICS and BIM-TMAN APPL Requirements

The APPL statement for CICS and/or BIM-TMAN must include thePARSESS=YES operand.



CICS Definitions for BIMFTRBC

CICS requires a CONNECTION and a SESSIONS definition for each APPLstatement defined above:

CEDA DEFINE GROUP(FTR) CONNECTION(HA01) (NOTE 1) NETNAME(HOSTAFT1) (NOTE 2) ACCESSMETHOD(VTAM) (REQUIRED) PROTOCOL(APPC) (REQUIRED) SINGLESESS(NO) (REQUIRED) DATASTREAM(USER) (REQUIRED)

CEDA DEFINE GROUP(FTR) SESSIONS(HA01SESS) CONNECTION(HA01) (NOTE 1) MODENAME(APPC) (NOTE 3) PROTOCOL(APPC) (REQUIRED) MAXIMUM(1,1) SENDSIZE(4096) RECEIVESIZE(4096)

NOTES:

1) CONNECTION name HA01 can be any value you desire, but must be uniquefor each definition, and must be the same for the SESSIONS andCONNECTION definitions.

2) NETNAME must be the name defined to VTAM for each APPL.

3) APPC must be the name of the LOGMODE defined to VTAM for APPCsessions. It must be contained in the MODETAB= specified on the VTAMAPPL statement for the CICS system.

4) If you define a new group for these CEDA definitions, remember to add thenew group to your existing CICS startup list and using the CEDA installfunction to activate the new definitions:

CEDA ADD GROUP(FTR) LIST(yourlist)CEDA INSTALL GROUP(FTR)

APPC connections with CICS require the following SIT operand:

ISC=YES,



VSE JCL to Execute BIMFTRBC

The following JCL is required to execute BIMFTRBC in VSE:

// LIBDEF PHASE,SEARCH=lib.sublib// EXEC BIMFTRBC,SIZE=AUTO,PARM='UP parms'OPTION ...CONNECT ...HOSTAFT .../*/&

MVS JCL to Execute BIMFTRBC

The following JCL is required to execute BIMFTRBC in MVS:

//STEPn EXEC PGM=BIMFTRBC,PARM='UP parms'//STEPLIB DD DSN=bimpctfr.loadlib,DISP=SHR//SYSPRINT DD SYSOUT=*//SYSIN DD *OPTION ...CONNECT ...HOSTAFT .../*//

Commands and Operands for BIMFTRBC

Parameter cards must be supplied to program BIMFTRBC to establish the APPCconnection to the host side of BIM-PC/TRANSFER, and to specify whichHOSTAFT scripts are to be activated. The syntax of the commands is the same asfor program BIMFTRPR. Refer to section “Syntax” on page 262 for moreinformation.



OPTION Command

The OPTION Command is used to override certain processing options ofBIMFTRBC. This command is optional. If omitted, the specified defaults areused.

The APPLRETRY, APPLSTOP and APPLWAIT operands control howBIMFTRBC searches a VTAM APPL pool that has been defined for its use. Referto section “VTAM Definitions for BIMFTRBC” on page 164 for more informationon VTAM APPL pools. These operands are used in conjunction with the APPLIDoperand of the CONNECT Command.

How to enter

OPTION - [APPLRETRY(10|nnnn) -] [APPLSTOP(5|nnnn) -] [APPLWAIT(30|nnnn)]

Explanation

APPLRETRY(10|nnnn)

This operand specifies how many times BIMFTRBCshould scan the VTAM APPL pool looking for anavailable APPL.

APPLSTOP(5|nnnn)

This operand controls when the end of a pool isdetected. It specifies how many consecutive VTAMAPPLs it needs to attempt to use that have a status ofeither inactive or not found, before it assumes it hasreached the end of the APPL name pool.

APPLWAIT(30|nnnn)

This operand specifies how long BIMFTRBC should waitafter it has completed a scan of the VTAM APPL poolbefore starting the next scan. For VSE, this value isspecified in seconds. For MVS, this operand is specifiedin minutes and seconds (mmss).



CONNECT Command

The CONNECT Command is used to provide the values required to establish theAPPC connection to the host side of BIM-PC/TRANSFER. This command mustappear prior the the first HOSTAFT command.

How to enter

CONNECT - APPLID(xxxxxxxx) - TOAPPLID(xxxxxxxx) - [LOGMODE(APPC|xxxxxxxx) -] [TRANID(FTRT|xxxx)]

Explanation

APPLID(xxxxxxxx)

This operand specifies the name of the VTAM APPL tobe used for the batch side of the APPC connection. If youhave defined a pool of APPLs to VTAM, specify thename of the first entry in the pool. Refer to section“VTAM Definitions for BIMFTRBC” on page 164 formore information on VTAM APPL pools.

TOAPPLID(xxxxxxxx)

This operand specifies the name of the VTAM applid ofthe CICS or BIM-TMAN that contains the host side ofBIM-PC/TRANSFER.

LOGMODE(APPC|xxxxxxxx)

This operand specifies the name of the VTAM logmodethat you have defined for APPC connections. This mustmatch the name defined in the CICS SESSIONSdefinition.

TRANID(FTRT|xxxx

This operand specifies the transaction id of the host sideof BIM-PC/TRANSFER. You can omit this operand ifyou are using the default FTRT.



HOSTAFT Command

The HOSTAFT Command is used to activate a specific HOSTAFT Script forprocessing You can specify as many of these commands as you need in the samejob stream. They must follow a CONNECT Command.

If any errors are detected activating a script, the jobstep completion code is set to12.

How to enter

HOSTAFT - SCRIPT(‘script name’) - [JOBNAME(jobname) -] [UP1(xxxxxxxx) -] [UP2(xxxxxxxx) -] [UP3(xxxxxxxx) -] [UP4(xxxxxxxx) -] [UP5(xxxxxxxx) -] [UP6(xxxxxxxx) -] [UP7(xxxxxxxx) -] [UP8(xxxxxxxx) -] [NOWAIT|WAIT]

Explanation

SCRIPT(‘script name’)

This operand specifies the name of the HOSTAFT Scriptto be activated. If the name of the script contains spaces,enclose the value in quotes.

JOBNAME(jobname)

This operand can be used to override the name of the jobthat is recorded with the activated script. If this operandis omitted, the name of the current job is used. For VSE,this is the VSE job name, not the POWER job name.

UP1(xxxxxxxx) - UP8(xxxxxxxx)

These operands provide values to be used for variablesubstitution in the HOSTAFT Script. These can be usedto vary the execution of a specified script, based on theactivation operands. Any of these operands that areomitted will default to the value, if any, specified in theUPARM Command.

NOWAIT|WAIT

This operand can be used to cause the initiating jobstream to wait for the activated script to complete beforecontinuing. If NOWAIT is specified, or allowed to



default, the initiating job stream does not wait for thescript to complete.



UPARM Command

The UPARM Command is used to provide defaults for the ‘UPn’ operands of theHOSTAFT Command. It is intended to be used as a PARM= on the EXEC. Ifspecified as a SYSIN command, it must precede any HOSTAFT Command thatrequires it.

How to enter

SYSIN:

UPARM|UP - UP1(data) - UP2(data) - UP3(data) - UP4(data) - UP5(data) - UP6(data) - UP7(data) - UP8(data) -

PARM=:

PARM='UP UP1(data) UP2(data) ... UP8(data)'

Explanation

UPn

Specifies the substitution data for each of the UPARMvariables %UP1 - %UP8.

The data for each variable can be from 0 to 8 charactersin length. Any variables not specified will be assumed tobe length 0.



Activating a HOSTAFT Script with a CICS Application

BIM/PC/TRANSFER includes an interface that your CICS Command-Levelapplications can use to activate a HOSTAFT Script for processing. To activate ascript, your applications simply need to complete and pass a suppliedCOMMAREA to program ‘BIMFTRHC’ using a standard EXEC CICS LINKcommand.

Two copybooks have been included, one for COBOL programs and one forAssembler programs:

VSE: BIMFTRHC.CBIMFTRHC.A

COBOLAssembler

MVS: BIMFTRHCBIMFTRHA

COBOLAssembler

The COMMAREA to be passed to BIMFTRHC is 200 bytes in length. Yourapplication should initialize the entire area to low-values before filling in theindividual fields. The following table lists the fields in the COMMAREA. TheCOBOL names are used; for Assembler, drop the BIMFTRHC- prefix:

BIMFTRHC-FTHCAREA Group name for the entire COMMAREA

BIMFTRHC-FTHCID Eyecatcher. This field must be initialized to‘HOSTAFT’ as a left justified, space filled, 8-byte name.

FILLER 8-byte unused area.

BIMFTRHC-FTHCSRPN 16-byte field containing the name of theHOSTAFT Script to be activated.

BIMFTRHC-FTHCJOBN 8-byte job name to be recorded with the script.

BIMFTRHC-FTHCUPRM Group name for 8 UPARM fields to be used forvariable substitution in the script.

BIMFTRHC-FTHCPRM1BIMFTRHC-FTHCPRM2BIMFTRHC-FTHCPRM3BIMFTRHC-FTHCPRM4BIMFTRHC-FTHCPRM5BIMFTRHC-FTHCPRM6BIMFTRHC-FTHCPRM7BIMFTRHC-FTHCPRM8

8 fields for UPARM variables. Each field is 8-bytes in length.

BIMFTRHC-FTHCWAIT 1-byte field. Set this field to ‘W’ if you wantyour application to wait for the scriptprocessing to be completed. If this field is notset to ‘W’, the script will be activated forprocessing, and control will be returned toyour application without waiting for thetransfer(s) to complete.



FILLER 12-byte unused area.

BIMFTRHC-FTHCMSGA Group name for the message response area.This is an 83-byte area.

BIMFTRHC-FTHCRC 2-byte return code. This is the first twopositions of the message response area. It willcontain one of the following values:

OK activation completed OK

NF script not found

IV Other invalid condition

FILLER This field will contain a comma if the returncode is not ‘OK’

BIMFTRHC-FTHCMSG 80-byte message text if the return code is not‘OK’.

After your application has completed building the COMMAREA, link to BIM-PC/TRANSFER using the following CICS Command:

EXEC CICS LINK PROGRAM('BIMFTRHC'),COMMAREA(BIMFTRHC-FTHCAREA),END-EXEC.

After the link has completed, check the BIMFTRHC-FTHCRC for ‘OK’ if not,display the returned error message text for problem resolution.


Page 174 File Upload Scripts

File Upload ScriptsA File Upload Script is a sequence of data lines and control statements whichoperate together as instructions for BIM-PC/TRANSFER during a file upload.

File Upload Scripts can be used to:

• Wrap host JCL or other data lines around a PC file.• Concatenate multiple PC files into one host file.

Scripts are standard PC ASCII files that can be created with any PC text editor. Ifyou use a word processor to create the script, be sure to save the script as a plaintext file, not a word processing document.

Upload Scripts can be specified by the PC user for any upload by selecting the“Script File” check box on the File Dialog box.

If an upload script is specified, both the CRLF and TRANSLATE options areassumed to be “YES”.

The File Upload Script consists of 8 different kinds of statements:

Command Description Page#OPTION Processing Options 175#PROMPT User Prompt for processing options 177@name Label 179#IF If 180#INCLUDE Include file 181#GOTO Go to 182data line Data to be uploaded to host 183#END End of script 184

Each of these is described below.

Notes on Syntax:• Words in UPPER CASE must be keyed in upper case.

• Words in lower case indicate places where you may be creative in assigningnames to things, or where several options exist for the entry.

• Individual operands within statements are separated by spaces.


File Upload Scripts Page 175

Processing Options

Processing options can be imbedded in the script. There are four different optionsthat can be specified. The defaults in effect are highlighted in the modelstatement below. You only need to supply an #OPTION statement if you need tochange one or more of the settings.

If specified, this must be the first line in the File Upload Script.

#OPTION DATEFMT=mm/dd/yy CMDPFX=# LBLPFX=@ VARPFX=% CONTINUE=-

DATEFMT=mm/dd/yy

This operand defines the format for the variable“%DATE”. The date format can be specified in any wayyou want. The format can be made up of anycombination of the following values:MM Two digit month number (01 = January)DD Two digit day within monthYY Two digit year (94,95, etc.)YYYY Four digit year (1994, 2002, etc.)M3 Three character month abbreviation (JAN,

FEB, etc.)MONTH Full month nameDDD Relative day of year (Julian).

The default is “MM/DD/YY”

Examples:

DATEFMT=MM-DD-YY 07-21-94DATEFMT=MM/DD/YYYY 07/21/1994DATEFMT=YY-MM-DD 94-27-21DATEFMT='M3 DD, YYYY' JUL 07, 1994DATEFMT=YYYY:DDD 1994:202

CMDPFX=#

This operand defines the character that marks thebeginning of a command line. If any of the data lines thatwill be contained in the script begin with a '#', then youmust specify a character here that does not appear at thestart of any data line. You must also use your selectedcharacter to begin all commands except the #OPTION.

LBLPFX=@

This operand defines the character that marks thebeginning of a label line. If any of the data lines that willbe contained in the script begin with a '@', then you must



specify a character here that does not appear at the startof any data line.

VARPFX=%

This operand defines the character that marks thebeginning of a variable name. If any of the data lines thatwill be contained in the script contain a '%', then youmust specify a character here that does not appear in anydata lines.

CONTINUE=-

This operand defines the character that marks thecontinuation of a script statement. If any of the data linesthat will be contained in the script end with a '-', thenyou must specify a character here that does not appear atthe end of any data line.



#PROMPT

The #PROMPT statement can be used to request input from the PC user prior tostarting a file upload.

#PROMPT %fldname DEFAULT=default - TYPE=X|N - RANGE=(from,to) - LIST=(xxx,yyy,zzz,...) - HDG='heading text' - LENGTH=n

You can specify as many #PROMPT statements as required for your script. Theymust all appear at the beginning of your script. If you are using the #OPTIONcommand, the #PROMPT statements must follow the #OPTION.

The #PROMPT statement can be continued to multiple script lines by specifyingthe character specified for the CONTINUE= operand of the #OPTION statementas the last character of each line except the last line of the statement.

%fldname

Required. This is the field identifier that can appear in asubsequent #IF statement. 'fldname' can be any characters, up to8 in length. The '%' is required as the first character. If theVARPFX= operand of the #OPTION statement has beenspecified, use the value for that operand in place of the '%'.

LENGTH=n


DEFAULT=default


Note: If a LIST operand is provided, and the DEFAULT operandis omitted, the first value in the LIST is used for the default.

TYPE=X|N

Specifies the type of field. 'X' for character, 'N' for numeric. Thedefault is 'X'.

RANGE=(from,to)

Optional operand that provides range edits for data entered bythe PC user. If the field type is character, and the entered datacan contain spaces, the from and to values must be specified



within quotes. This operand is mutually exclusive with the LISToperand.


Optional operand that provides a list of valid responses that canbe entered by the PC user. If the field type is character, and theentered data can contain spaces, the individual values in the listmust be specified within quotes. This operand is mutuallyexclusive with the RANGE operand.

HDG='heading text'


Example:

#PROMPT %FLD1 HDG='Select Record Type' - LENGTH=7 - LIST=(MASTER,ACCT,LICENSE)

In this example, prompt field %FLD1 is defined as a 7 character field. The PCuser can respond with one of three choices: MASTER, ACCT or LICENSE. Theimplied default is MASTER.



Labels

The #IF statement (below) may cause processing to skip around within the FileUpload Script. The Label statement defines the location for processing tocontinue whenever a #IF statement is evaluated as true.

@name

name


If the LBLPFX= operand of the #OPTION statement has beenspecified, use the value for that operand in place of the '@'.

Example:

@HAPPYHOUR



#IF

The #IF statement allows you to jump around within the File Upload Script.


field

Is the %fldname from a #PROMPT statement.

condition



comparand

This is either a literal or a %fldname from a #PROMPTstatement. It will be compared to the field above. Literals thatcontain embedded spaces must be enclosed within single quotes.

label

This is the label name where processing will resume if thecomparison specified in the #IF statement evaluates to true. Ifthe comparison evaluates to false, the next sequential statementin the File Upload Script will be processed.


Example:

#IF %FLD1 = MASTER MASTER-RTN • • •@MASTER-RTN • • •



#INCLUDE

The INCLUDE causes a PC file to be uploaded to the host.

#INCLUDE filename [ERASE]

or

#INCLUDE FILEBOX='title for dialog box' label

filename

This specifies which PC file(s) are to be uploaded. It can be:

• A full PC filename including drive and path.• The %fldname from a #PROMPT.• A generic PC filename mask if more than one PC file is to be

selected.

ERASE

This operand causes the PC filename to be erased (deleted) uponsuccessful transfer to the host. Erasure will not take place untilall files that are part of the script have been sent to the host, andthe host has indicated success to the PC.

FILEBOX='title for dialog box'

This format of the #INCLUDE generates a standard file opendialog box with the specified title bar. The PC user selects thedesired file to be uploaded using the dialog box.

label

This is the label name where script processing will resume if the“CANCEL” button is pressed on the FILEBOX dialog. If thisoperand is omitted, pressing the “CANCEL” button willterminate the script. All data up to that point will be uploaded tothe host.



#GOTO


#GOTO label

label





data line

Any lines encountered in the script that does not contain either a script commandor a label will be passed to the host as data. Each line will first be examined forvariable substitution.


Variables can be inserted into data lines. These will be replaced prior to thetransmission to the host. Variables can come from #PROMPT statements, or oneof the following reserved words:

%DATE Today's date in the format specified in the#OPTION statement.

%TIME Time of day when the script was started. Theformat will be hh:mm:ss.

%USER The User ID of the PC user.%PWD The password of the PC user.



#END

This statement indicates the end of script processing.

#END

All scripts must have a #END as the last line. It must also begin in position 1.



Sample Script

#OPTION DATEFMT=DD-MM-YYYY* $$ JOB JNM=WORKIE,CLASS=A// JOB WORKIE* $$ LST CLASS=Q,DISP=D,USER='%USER %TIME'// EXEC WORKIERDATE %DATE#INCLUDE C:\WORK\STUFF\WKFIL ERASE/*/&* $$ EOJ


Page 186 Host Customization

Host Customization using the FTRM TransactionBIM-PC/TRANSFER uses definitions contained in a VSAM control file todetermine which types of transfers are allowed, and who is allowed to performthem.

This control file is maintained using the BIM-PC/TRANSFER transaction FTRM.The following types of information are maintained in the control file:

1) System Options These options affect the operation of BIM-PC/TRANSFER for all transfers and users.See page 191 for more information.

2) User Definitions These definitions define who is allowed touse BIM-PC/TRANSFER, and whichtransfers they are allowed to perform. Seepage 201 for more information.

3) Category Definitions These definitions define the types oftransfers that can be performed. See page195 for more information.

4) VSAM Profiles These definitions define the VSAMtransfers that can be performed. See page204 for more information.

5) SAM Profiles These definitions define the VSE SAMdataset transfers that can be performed.See page 210 for more information.

6) Script Definitions These definitions contain the selection andformatting rules for downloads and thescripts to be used for Host InitiatedAutomatic File Transfer (HOSTAFT). Seepage 216 for more information.

7) Dataset Access Definitions These definitions are used to define whichVSAM clusters can be transferred using thetransfer by Cluster name feature, whichPartitioned Datasets can be transferred,and which QSAM datasets can betransferred. See page 221 for moreinformation.

8) Access Security Definitions These definitions are used to limit access toitems in the various transfer categories notcovered by the Data Access Definitions.


Host Customization Page 187

See page 223 for more information.

9) HOSTAFT Status Records These records are used to monitor thestatus of HOSTAFT scripts that are beingprocessed by PC's. See page 244 for moreinformation.

10) TCP/IP Connection Options These definitions are used to control theactivation of the TCP/IP interface. Seepage 250 for more information.

For all FTRM screens, PF keys 13 - 24 work the same as the corresponding keys 1- 12.

You can define up to four transactions in addition to FTRM for maintaining andviewing various combinations of host definitions. Refer to “ALT MAINT TXNCODES“ on page 192 for additional information.

Adding / Changing Definitions

Adding, changing and deleting definitions is accomplished as follows:

Adding new definitions

1) Display a definition that is similar to the one you want to add by selectingthe definition from a “list” screen, or scrolling through the currentdefinitions. If you are about to add the first definition of a particular type,select the “definitions” screen from the System Menu, and a blank definitionentry will be displayed. To add the first Access Security Definition for aparticular category type, press PF2 from the Access Security Definitions listscreen, and select the desired type from the menu of available types.

2) Change the fields in the definition to reflect what the new definition shouldbe.

3) Press PF5 to add the new definition.

Updating definitions

1) Display the definition that is the one you want to update by selecting thedefinition from a “list” screen, or scrolling through the current definitions.

2) Change the fields in the definition to reflect what the updated definitionshould be.

3) Press PF2 to update the definition. If you changed the data in a key field forthe definition, you will be asked to press PF5 to add the new entry. If youdid not intend to change the key field, change the data back to its originalcontents and press PF2 again.


Page 188 Host Customization

Deleting definitions

1) Display the definition that is the one you want to delete by selecting thedefinition from a “list” screen, or scrolling through the current definitions.

2) Press PF12 to delete the definition. If you press PF12 when not intended,immediately press PF5 to re-add the deleted definition.

Replacing definitions

This procedure can be used to delete an existing entry, and re-add it using adifferent key:

1) Display the definition that is the one you want to replace by selecting thedefinition from a “list” screen, or scrolling through the current definitions.

2) Press PF12 to delete the definition.

3) Change the fields in the definition to reflect what the new definition shouldbe.

4) Press PF5 to add the new definition.


Host Customization Page 189

PF Key Summary

The following PF keys can be used by various screens. The bottom line of thescreen shows which PF keys are active for the current screen.

PF2=UPDATE Causes the current definition to be updated.

PF3=END Terminates the FTRM transaction and returns to CICSor BIM-TMAN.

PF4=RETURN Returns from the definition screen to either the “List”screen, or the “Menu” depending on how you got tothe definition screen.

Returns from the “List” screen to the “Menu”.

PF5=ADD Causes a new definition to be added using the currentkey and data.

PF6=TOP Redisplay from the top of the current entry list.

PF6=(<) Shift screen to the left to view additional array fields.

PF7=PREV Scrolls to the previous definition.

PF8=NEXT Scrolls to the next definition.

PF8=SCROLL Displays the next “List” screen of definitions.

Pressing this key when the last screen of definitions isbeing displayed will resume the display from the firstdefinition.

PF9=BOT Display the last screen of the current entry.

PF9=(>) Shift screen to the right to view additional array fields.

PF10=UP Display the previous screen of the current entry.

PF11=DOWN Display the next screen of the current entry.

PF12=DELETE Causes the current definition to be deleted.

If this key is pressed by accident, immediately pressPF5 to re-add the definition.

For all FTRM screens, PF keys 13 - 24 work the same as the corresponding keys 1- 12.


Page 190 (System Menu) Host Customization

System Menu

When you first enter the transaction FTRM, or one of the four alternatetransactions allowed, the System Menu will be displayed:

*** BIM-PC/TRANSFER *** SYSTEM MENU yyyy/mm/dd hh:mm:ss

_ CATEGORY DEFINITIONS _ CATEGORY DEFINITION LIST _ USER DEFINITIONS _ USER DEFINITION LIST _ VSAM PROFILE DEFINITIONS _ VSAM PROFILE LIST _ SAM PROFILE DEFINITIONS _ SAM PROFILE LIST _ SCRIPT DEFINITIONS _ SCRIPT DEFINITIONS LIST _ DATASET ACCESS DEFINITIONS _ DATASET ACCESS LIST _ HOSTAFT STATUS DETAIL _ HOSTAFT STATUS LIST _ HOSTAFT ACTIVATE SCRIPT _ SYSTEM OPTIONS _ ACCESS SECURITY DEFINITIONS _ TCP/IP CONNECTION OPTIONS

SELECT DESIRED AREA AND PRESS ENTER PF3=END RELEASE x.xx

If you use an alternate maintenance transaction code, the format of this menuwill vary depending on the menu options selected for the transaction code youare using. Refer to “ALT MAINT TXN CODES“ on page 192 for additionalinformation.

To select an area from the menu, tab down to the desired area, key a non-blankprior to the description and press ENTER. If no area has been selected whenENTER is pressed, the line containing the cursor is selected.

The areas described as a “LIST” will display a selection list of all available entriesof the described type. The areas described as “DEFINITIONS” will display thefirst entry of the specified type. Scroll PF keys are provided to move between thevarious entries.


Host Customization (System Definition) Page 191

System Options Screen

The following screen is displayed when the “SYSTEM OPTIONS” entry isselected on the System Menu:

*** BIM-PC/TRANSFER *** SYSTEM OPTIONS yyyy/mm/dd hh:mm:ss

DEFAULT SECURITY EXIT: ________

REQUIRE USER DEFINITION: N DEFAULT USER DEFINITION: ________

DEFAULT TRANSLATE TABLE: ________

GENERATE EVENT LOG: N

TRAN MENU OPTIONS ==== ============ ALT MAINT TXN CODES: FTRH NNNUNUUNNNNN FTRU IIIIIIIIIIII ____ NNNNNNNNNNNN ____ NNNNNNNNNNNN

MAKE DESIRED CHANGES AND PRESS PF2PF2=UPDATE, PF3=END, PF4=RETURN

The options on this screen are used to control the entire BIM-PC/TRANSFERsystem.

DEFAULT SECURITY EXIT

This option specifies the name of a user provided security exit. This name mustmatch an existing program defined to CICS.

The exit specified for this option will be invoked for any access to a “CategoryDefinition” that does not specify a specified security exit for the SECEXIToperand.

Refer to the section “User Security Exits” on page 379 for details on how to writeyour own security exit.

REQUIRE USER DEFINITION

This option can be specified as 'Y', 'N' or R' and specifies whether or notBIM-PC/TRANSFER should require that a matching “User Definition” bepresent for a transfer to be allowed.

The default is 'N' meaning that all transfers are allowed by anyone using any ofthe defined “Category Definitions”, unless a user supplied security exit has beenprovided or the field DEFAULT USER DEFINITION is used. Any attempt tologon using a blank User ID, or a User ID that has not been defined, will result inthe “Default User Definition” being used.

'Y' indicates that all PC users must logon using a valid User ID.


Page 192 (System Definition) Host Customization

'R' stands for ‘required’ and is similar to 'N' except that if a non-blank User ID isentered by the PC user, it must be defined.

DEFAULT USER DEFINITION

This field is used to provide the User ID to be used as a Default for securitypurposes, when none is supplied by the PC user. The User Id specified here mustalready have been defined. Refer to section “Default Security Mode” starting onpage 77 for more information.

DEFAULT TRANSLATE TABLE

This option specifies the name of a user provided translate table. This name mustmatch an existing program defined to CICS.

The translate table is used for conversion between EBCDIC and ASCII.

The table is 512 bytes long, containing two 256 byte translate tables. The firsttable is used to convert EBCDIC to ASCII. The second table is used to translateASCII to EBCDIC.

If no name is provided here, the supplied table BIMFTRTT is used. Refer to thesection “Default Translate Tables” on page 388 for a description of this table.

GENERATE EVENT LOG

This Y/N option specifies whether or not to generate entries for each transfer inthe Host Activity Log.

ALT MAINT TXN CODES

These fields provide for up to four additional CICS / BIM-TMAN transactioncodes that be defined for viewing and maintaining the BIM-PC/TRANSFER hostdefinitions.

For each of the four transaction codes, you specify which types of entries can bedisplayed, and whether the display is to allow updates, or is for viewing only.You must also define a CICS or BIM-TMAN transaction entry for each alternatetransaction. Use the definition for transaction FTRM as a basis, and then changethe transaction security as desired.

If a transaction is defined to CICS / BIM-TMAN that is not contained in thistable, such as FTRM, all menu options are assumed to be “U” giving full updateaccess to all definitions.

TRAN these fields contain the CICS / BIM-TMAN transaction codes to beused.

MENU OPTIONSthese fields contain twelve flags that indicate which types ofdefinitions can be viewed, and whether or not each type can beupdated.


Host Customization (System Definition) Page 193

NNNNNNNNNNNN|||||||||||||||||||||SAM profiles|||||||||TCP/IP Connection Options||||||||Access Security Definitions|||||||System Options||||||HOSTAFT Script Activation|||||HOSTAFT Status Records||||Dataset Access Definitions|||Script Definitions||VSAM profiles|User DefinitionsCategory Definitions

each option position can one of the following:

N access not allowedI inquiry/view access onlyU full update support

If inquiry/view access is specified for “User Definitions”, userpasswords are not displayed.


Page 194 (Category Definitions) Host Customization

Category Definition List

The following screen is displayed when the “CATEGORY DEFINITION LIST”entry is selected on the System Menu:

*** BIM-PC/TRANSFER *** CATEGORY DEFINITION LIST yyyy/mm/dd hh:mm:ss

CMD CATEGORY LIBQUE DESCRIPTION --- -------- ------------------------- ---------------------------------------- _ EDIT SJA BIM-EDIT Library Access _ EDIT BIM-EDIT Library Access _ POWER POWER Queue Access

CMD VALUES ARE: (S)ELECT, (D)ELETE PF3=END, PF4=RETURN, PF8=SCROLL

This screen is used to scroll through all of the “Category Definitions” that havebeen defined to BIM-PC/TRANSFER.

You can display the detail for a specific definition by entering 'S' in the CMD linefor a desired entry and pressing ENTER. If no lines contain an 'S', the linecontaining the cursor will be selected.

You can delete unneeded entries by entering 'D' in the CMD line(s) for the entriesto be deleted and pressing ENTER.

If you have more definitions than can be displayed on a single screen, press PF8to scroll through the available entries. When the last screen of entries has beendisplayed, pressing PF8 will resume from the first entry.

Pressing PF4 will return you to the “System Menu”. Pressing PF3 will terminatethe FTRM transaction.


Host Customization (Category Definitions) Page 195

Category Definition Screen

The following screen is displayed when the “CATEGORY DEFINITIONS” entryis selected on the System Menu, or when an entry is selected from the“CATEGORY DEFINITION LIST” screen:

*** BIM-PC/TRANSFER *** CATEGORY DEFINITIONS yyyy/mm/dd hh:mm:ss

CATEGORY: ________ LIBQUE: ____________________________________________ DEFAULT: N

DESC: ________________________________________ TYPES: B (U)PLOADS, (D)OWNLOADS, (B)OTH UPLOADS NEW: Y REPLACE: Y APPEND: Y (ALLOWED Y/N) SECEXIT: ________ SECGRP: ________ ACCESS SECURITY GROUP: ________ EXIT: ________ DRIVER: ________ driver description area DRIVER DATA: ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________

CRLF: * TRANSLATE: * TRTABLE: ________

MAKE DESIRED CHANGES AND PRESS PF2 TO UPDATE, PF5 TO ADDPF2=UPDATE, PF3=END, PF4=RETURN, PF5=ADD, PF7=PREV, PF8=NEXT, PF12=DELETE

This screen is used to add, update or delete “Category Definitions”. Refer to thesection “Adding / Changing Definitions” on page 187 of this chapter for generalinformation about the use of this screen.

Category Definitions are the main control point in BIM-PC/TRANSFER. Theydetermine which transfers may occur.

When a PC user signs on to BIM-PC/TRANSFER, the signon is sent to the host,where the Category Definitions are searched. All definitions that are authorizedfor the PC user, based on the SECGRP and any supplied User Security Exit, aresent to the PC. These definitions are used on the PC to generate selection menusand field entry dialogs for requesting uploads and downloads to the variouscategories.

Key Fields

Category Definitions are keyed by CATEGORY and LIBQUE. Any change toeither value will require that the new entry be added, and possibly the old entrybe deleted.

Only one Category Definition can exist with the same CATEGORY and LIBQUEspecification.

CATEGORY

This is an internal name assigned by you. Typically the name should representthe host source/destination of the transferred data, such as POWER, EDIT, ICCF,etc.



When a PC user signs on to BIM-PC/TRANSFER, the host will send alldefinitions authorized for the PC user that have unique values for CATEGORY.

This value is used by the PC when requesting inquiries or transfers to beperformed.

LIBQUE

This value is used to restrict transfers of certain data within a CATEGORY. Thecontents of LIBQUE is dependent on the DRIVER used. The following tablesdefine each of the supported drivers and the LIBQUE usage:

Common:Driver Access LIBQUEBIMFTRDC VSAM Cluster Access VSAM Cluster Name

BIMFTRDE BIM-EDIT Libraries Library Name

BIMFTRDM CICS Temporary Storage TS Queue Name

BIMFTRDT CICS Transient Data Transient Data Queue

BIMFTRDV VSAM Dataset access VSAM Profile name

BIMFTRDX Script Definitions Script name

VSE Only:Driver Access LIBQUEBIMFTRD$ IND$ Host Transfer File FileName

BIMFTRDB VSE Library Lib.Sublib

BIMFTRDF SAM datasets SAM Profile name

BIMFTRDF BIM-EPIC datasets Dataset name

BIMFTRDI ICCF Library nnn (library number)

BIMFTRDL VSE Library Lib.Sublib

BIMFTRDP POWER Queues xxx (RDR,LST,PUN)

BIMFTRDR VSE Library via BIM-EDIT Lib.Sublib

MVS Only:Driver Access LIBQUEBIMFTRDD Partitioned Datasets Dataset name

BIMFTRDJ JES Queues xxx (Held,Output,IRDR)

BIMFTRDQ QSAM Datasets Dataset name

When a transfer request is made from the PC, the LIBQUE specified in the PCrequest is matched against the values specified in the various CategoryDefinitions with the specified CATEGORY. If no match is made, the request isrejected.



The value for LIBQUE can be specified as a generic term:

TEST* means match all LIBQUEs that start with TEST*TEST* means match all LIBQUEs that contain TESTTEST*ONE means match all LIBQUEs that start with TEST and end

with ONETEST?ONE means match all LIBQUEs that start with TEST, contain

any character after TEST, and then end with ONE* (or blanks) means match all LIBQUEs

DEFAULT

This field can be specified as ‘Y’ or ‘N’. It defaults to ‘N’.

If ‘Y’ is specified, it means that the LIBQUE value is to be used as a default forany download requests from the PC that do not specify a LIBQUE value.

For example, if you defined a Category Definition for VSAM access and specifieda LIBQUE of “FILE*”, defining it as a DEFAULT, then any download requestsfrom a PC that did not specify a “VSAM Profile Name” would get a directorydialog of all VSAM profiles that begin with “FILE*”.

If you want to get a directory of all entries from a Category Definition that isdefined as a DEFAULT, the PC user must specify “*” in the correspondingLIBQUE field in the PC download dialog. The LIBQUE field is always the firstfield in the download dialog.

DESC

This is a description for this definition. It is sent to the PC during the signon, andis displayed in a menu selection list for the PC user to select the origin ordestination of a specific transfer. It may be specified in upper and lower case.

TYPES

This field specifies the types of transfers that can be requested for the specifiedCATEGORY and LIBQUE:

U Uploads from the PC to the HostD Downloads from the Host to the PCB Both Uploads and Downloads (the default)

The first Category Definition for each CATEGORY name should either bespecified as a ‘B’, or should be the same as all other definitions defined with thesame CATEGORY name. This is because the PC uses the setting from the firstdefinition for each CATEGORY name to determine which dialogs an entry is toappear in.

UPLOADS NEW / REPLACE / APPEND

These fields can be used to restrict the types of uploads that can be performed.They restrict the use of the NEW, REPLACE and APPEND options. If you specify'N' for an option, it will not be allowed.



SECEXIT

This is the name of an optional security exit to be called for all transfer requestsagainst this Category Definition. This name must match an existing programdefined to CICS.

Refer to the section “User Security Exits” on page 379 for details on how to writeyour own security exit.

SECGRP

This is a name assigned by you if you wish to restrict the use of this CategoryDefinition to specific PC users.

If a value is specified here, then any user that has a “User Definition” must havethe same value listed in the GROUPS section of the User Definition or the transferrequest will be rejected by BIM-PC/TRANSFER. See page 202 for moreinformation.

ACCESS SECURITY GROUP

This is a name assigned by you if you wish to restrict the use of this CategoryDefinition.

If a value is specified here, then it must match the name CATGRP name of anAccess Security Definition. See page 223 for more information.

EXIT

This is the name of an optional Formatting / Selection Exit that you can providefor certain Categories. This name must match an existing program defined toCICS.

Only certain DRIVER modules have support for this exit. Refer to the section“Format / Selection Exits” on page 383 for more information.

DRIVER

This is the name of the host processing program that services the transferrequests for this CATEGORY and LIBQUE. This name must match an existingprogram defined to CICS.

All CATEGORY definitions that use the same CATEGORY name must use thesame DRIVER.

Refer to the list of valid drivers on page 196 for field "LIBQUE", and review thesection “Driver Specifications” starting on page 306 for each driversconsiderations.

After you enter a driver name, a description is displayed to the right of the drivername. Make sure the description describes the type of transfer for which theCATEGORY is intended.



DRIVER DATA

These fields contain special processing options unique to each DRIVER thatcontrol how it functions in your environment. Refer to the section “DriverSpecifications” starting on page 306 for the options available for each driver.

CRLF

This field determines the default for carriage-return and line-feed insertion if thePC transfer request does not specify it:

* Let the DRIVER determine the option.Y For uploads to the host, the data has CRLF's separating each record. For

downloads to the PC, each record will be separated by a CRLF.N The records are not separated by CRLF's. Use the LRECL specified by

the PC, or the default LRECL determined by the DRIVER to separatethe input into records during an upload.

Refer to the section “Driver Specifications” starting on page 306 for moreinformation on the CRLF option.

TRANSLATE

This field determines the default for EBCDIC/ASCII translation processing if thePC transfer request does not specify it:

* Let the DRIVER determine the option.Y For uploads to the host, the incoming data will be translated from

ASCII to EBCDIC. For downloads to the PC, the data will be translatedfrom EBCDIC to ASCII.

N No translation will be performed.

Refer to the section “Driver Specifications” starting on page 306 for moreinformation on the TRANSLATE option.

TRTABLE

This is the name of the translate table to be used for EBCDIC / ASCII translationsfor this CATEGORY and LIBQUE. This name must match an existing programdefined to CICS. Refer to the field “DEFAULT TRANSLATE TABLE” in section“System Options Screen” starting on page 191 for more information.


Page 200 (User Definitions) Host Customization

User Definition List

The following screen is displayed when the “USER DEFINITION LIST” entry isselected on the System Menu:

*** BIM-PC/TRANSFER *** USER DEFINITION LIST yyyy/mm/dd hh:mm:ss

CMD USER ID NAME --- -------- ---------------------------------------- _ ADMN ADMN User Name _ USER1 User 1 Name _ USER2 User 2 Name


This screen is used to scroll through all of the “User Definitions” that have beendefined to BIM-PC/TRANSFER.






Host Customization (User Definitions) Page 201

User Definition Screen

The following screen is displayed when the “USER DEFINITIONS” entry isselected on the System Menu, or when an entry is selected from the “USERDEFINITION LIST” screen:

*** BIM-PC/TRANSFER *** USER DEFINITIONS yyyy/mm/dd hh:mm:ss

USER ID: ________ PASSWORD: ________ NAME: ________________________________________

GROUPS: ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________

CATEGORY USER ID PASSWORD CATEGORY USER ID PASSWORD ======== ======== ======== ======== ======== ======== ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________

DATASET ACCESS- UP: ________ DN: ________


This screen is used to add, update or delete “User Definitions”. Refer to thesection “Adding / Changing Definitions” on page 187 of this chapter for generalinformation about the use of this screen.

User Definitions are required by BIM-PC/TRANSFER by each user that signs onfrom a PC if the “REQUIRE USER DEFINITION” option is specified on the“System Definition” screen.

If that option is not specified, users that sign on without a “User Definition” willbe allowed to use all “Category Definitions” to perform transfers.

Key Fields

User Definitions are keyed by USER ID. Only one User Definition may exist foreach USER ID specification.

USER ID

This is the id of the user that is specified during the PC signon toBIM-PC/TRANSFER.

PASSWORD

This is the password of the user that is specified during the PC signon toBIM-PC/TRANSFER. If you are using a maintenance transaction code that onlyhas inquiry/view access to user definitions, this field will be blank.


Page 202 (User Definitions) Host Customization

If this field is left blank, BIM-PC/TRANSFER will not require that the passwordmatches at PC signon. It will be assumed that you have specified a User SecurityExit, and that the exit will check the password at signon.

NAME

This is the name of the user. This is not currently used by BIM-PC/TRANSFER. Itis provided on this screen for your information.

GROUPS

These 40 fields are used to define the SECGRPs of “Category Definitions”,"Dataset Access Definitions", "Access Security Definitions" and "VSAM Profiles"that this user is authorized to use for transfers. You can specify these names inany sequence, they will be sorted alphabetically.

CATEGORY USER ID PASSWORD

These 8 sets of fields can be used to specify alternate USER ID and PASSWORDsto be passed to the DRIVERs of specific CATEGORYs.

These fields can be used, for example, if a users ID and/or PASSWORD aredifferent for BIM-EDIT and the VSE Interactive Interface (IND$).

If you are using a maintenance transaction code that only has inquiry/viewaccess to user definitions, the password fields will be blank.

DATASET ACCESS UP / DN

These two fields can be used to specify the names of Dataset Access Definitionsto be examined during uploads (UP) and downloads (DN). These definitions areused during VSAM transfers that are using either the "Cluster Name TransferFeature" of driver BIMFTRDV or the VSAM Cluster driver BIMFTRDC, and bothPDS and QSAM transfers in MVS. If Dataset Access names are specified here,only datasets defined in those definitions can be specified by the user fortransfers. Refer to the section "Dataset Access Definition Screen" on page 221 formore information.


Host Customization (VSAM Definitions) Page 203

VSAM Profile List

The following screen is displayed when the “VSAM PROFILE LIST” entry isselected on the System Menu:

*** BIM-PC/TRANSFER *** VSAM PROFILE LIST yyyy/mm/dd hh:mm:ss

CMD PROFILE DESCRIPTION DATASET --- ---------------- ---------------------------------------- -------- _ ESDS Process BIMESDS Dataset BIMESDS _ KSDS Process BIMKSDS Dataset BIMKSDS _ RRDS Process BIMRRDS Dataset BIMRRDS _ VSAM-FB Process Fixed Length VSAM Clusters BIM$FB _ VSAM-VB Process Variable Length VSAM Clusters BIM$VB


This screen is used to scroll through all of the “VSAM Profiles” that have beendefined to BIM-PC/TRANSFER.



If you have more profiles than can be displayed on a single screen, press PF8 toscroll through the available entries. When the last screen of entries has beendisplayed, pressing PF8 will resume from the first entry.



Page 204 (VSAM Definitions) Host Customization

VSAM Profile Definition Screen

The following screen is displayed when the “VSAM PROFILE DEFINITIONS”entry is selected on the System Menu, or when an entry is selected from the“VSAM PROFILE LIST” screen:

*** BIM-PC/TRANSFER *** VSAM PROFILE DEFINITIONS yyyy/mm/dd hh:mm:ss

PROFILE: ________________ DESC: ________________________________________

SECGRP: ________ DATASET ACCESS- UP: ________ DN: ________ DATASET: ________ E(X)IT/(S)CRIPT: _ NAME: ________________ TRANSLATE: * TYPES: _ (U)PLOADS, (D)OWNLOADS, (B)OTH CRLF: N CLUSTER: ____________________________________________ UCAT: ________

START KEY: 1-32: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HEX: 0000000000000000000000000000000000000000000000000000000000000000 33-64: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HEX: 0000000000000000000000000000000000000000000000000000000000000000

END KEY: LENGTH: 00 1-32: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HEX: 0000000000000000000000000000000000000000000000000000000000000000 33-64: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HEX: 0000000000000000000000000000000000000000000000000000000000000000


This screen is used to add, update or delete “VSAM Profile Definitions”. Refer tothe section “Adding / Changing Definitions” on page 187 of this chapter forgeneral information about the use of this screen.

VSAM Profiles are required in BIM-PC/TRANSFER to perform VSAM datasettransfers using driver BIMFTRDV. These are not used for VSAM Clustertransfers using driver BIMFTRDC.

The PC requests a VSAM transfer using driver BIMFTRDV by specifying aCATEGORY name and a VSAM PROFILE name.

The VSAM Profile provides the name of the VSAM dataset, the name of anyformatting exit or script required, whether uploads and/or downloads aresupported for the dataset, and for downloads, the key range, if any, to be used.

For most VSAM profiles that will be used for specific VSAM datasets defined toCICS or BIM-TMAN, the only fields you should need to enter are:

• PROFILE the name the PC will specify• DESC optional description displayed on PC• DATASET DLBL/DD name (and CICS FCT name)• TYPES what types of transfers are allowed

Key Fields

VSAM Profiles are keyed by PROFILE name. Only one VSAM Profile can existwith the same PROFILE name.



PROFILE

This is an internal name assigned by you. Typically the name should representthe type of data being transferred.


DESC

This is displayed on the PC when inquires are requested for available VSAMprofiles.

SECGRP

This is a name assigned by you if you wish to restrict the use of this ProfileDefinition to specific PC users.


DATASET ACCESS UP / DN

These two fields can be used to specify the names of Dataset Access Definitionsto be examined during uploads (UP) and downloads (DN). These definitions areused during VSAM transfers that are using the "Cluster Name Transfer Feature".If Dataset Access names are specified here, only VSAM Clusters defined in thosedefinitions can be specified by the user for transfers.

DATASET

This is the DLBL/DD name of the VSAM dataset to be used for the transfer. ForCICS, the name specified here must be defined to your CICS FCT, and must beopen and enabled when the transfer is requested, unless the “Cluster NameTransfer Feature” is being used, or the OPEN/CLOSE driver data options arebeing used. Refer to the section “BIMFTRDV - VSAM Dataset Driver (UsingProfiles)” on page 370 for the OPEN and CLOSE driver data options. This field isrequired for all profiles.

Cluster Name Transfer Feature

If you specify a DATASET name that begins with 'BIM$', then this profile can usethe “Cluster name transfer feature”. This feature allows transfers of VSAMdatasets by specifying the Cluster name at the PC. If you want to perform VSAMtransfers via Cluster name, and you don't need any of the special processingoptions provided by the VSAM Profile, you will find it easier to use a CategoryDefinition created for driver "BIMFTRDC - VSAM Cluster Driver" as describedon page 315.



Do not include a DLBL or DD in your CICS or BIM-TMAN JCL for these profiles.BIM-PC/TRANSFER will automatically generate the DLBL/DD for each transfer,using the specific VSAM Cluster name and UCAT specified on the PC.

CICS Considerations:

The FCT entry for this DATASET must be defined with the proper attributes forthe VSAM Clusters you will be transferring. For newer releases of CICS, the FCTentry must be defined with FILSTAT=(UNENABLED,CLOSED). If your CICSrelease does not support UNENABLED, then useFILSTAT=(ENABLED,CLOSED). BIM-PC/TRANSFER will automatically openand close the dataset for each transfer. You may need to define several Profiles ifyou have different types of VSAM datasets, such as fixed or variable length files.The following FCT entries are examples of what is required. These sample FCTentries are included in source member BIMFTRS1 and for MVS, RDO DEFINEsare contained in BIMFTRJ3:

BIM$VB0 DFHFCT TYPE=DATASET, X DATASET=BIM$VB0, X FILSTAT=(UNENABLED,CLOSED), X ACCMETH=(VSAM), X SERVREQ=(READ,UPDATE,ADD,BROWSE,DELETE), X RECFORM=(VARIABLE,BLOCKED),LSRPOOL=NONE, X STRNO=2BIM$FB0 DFHFCT TYPE=DATASET, X DATASET=BIM$FB0, X FILSTAT=(UNENABLED,CLOSED), X ACCMETH=(VSAM), X SERVREQ=(READ,UPDATE,ADD,BROWSE,DELETE), X RECFORM=(FIXED,BLOCKED),LSRPOOL=NONE, X STRNO=2

BIM-PC/TRANSFER will ENQUEUE on the DATASET name, thus single-threading the transfer for each Cluster name.

If the seventh position of the DATASET name is numeric, BIM-PC/TRANSFERwill assume that multiple FCT entries have been provided, and will search for thefirst non-busy FCT entry for use during the transfer.

If you specify the DATASET name as BIM$FB3, it will be assumed that you haveprovided FCT entries with names: BIM$FB0, BIM$FB1, BIM$FB2 and BIM$FB3.This allows up to 10 FCT entries, and thus 10 concurrent transfers for each VSAMprofile.

BIM-TMAN Considerations:

No file definitions or JCL are required. The same Profile can be used for allVSAM dataset types, and transfers are not single-threaded as they are in CICS.The DATASET field should be specified as “BIM$”.



E(X)IT/(S)CRIPT

This field is used to designate whether or not a “Download Script” or a“formatting/selection exit” is to be used. Refer to the NAME field for additionalinformation:

S A script is to be used. The name of the “Download Script” is in the NAMEfield.

X A formatting/selection exit is to be used. The name of the exit is in theNAME field.

N Neither a script nor an exit is to be used.

NAME

This is the name of the script or formatting / selection exit to be used fortransfers.

An exit is required for all uploads of VSAM unless:

• You are running CICS 1.7 or above, and are uploading a fixed length KSDSfile, or

• The data from the PC is separated into records with CRLF’s.

An exit or script is only required for downloads if you wish to filter out selectedrecords, or to change the record formats prior to sending them to the PC.

Script names must match an existing “Download Script Definition” in the HostControl File. Only downloads are supported for scripts.

Exit names must match an existing program defined to CICS. Any namespecified here will override the EXIT specification of the “Category Definition”.Refer to the section “Format / Selection Exits” on page 383 for more information.

TRANSLATE


* Let the DRIVER determine the option.Y For uploads to the host, the incoming data will be translated from ASCII to

EBCDIC. For downloads to the PC, the data will be translated fromEBCDIC to ASCII.


A value of “Y” or “N” will override any specification in the “CategoryDefinition”. Refer to the section on each DRIVER's considerations starting onpage 306 of this manual for more information on the TRANSLATE option.

CRLF


* Let the DRIVER determine the option.



Y For uploads to the host, the data has CRLF's separating each record. Fordownloads to the PC, each record will be separated by a CRLF.

N The records are not separated by CRLF's. Use the LRECL specified by thePC, or the default LRECL determined by the DRIVER to separate the inputinto records during an upload.

A value of “Y” or “N” will override any specification in the “CategoryDefinition”. Refer to the section on each DRIVER's considerations starting onpage 306 of this manual for more information on the CRLF option.

TYPES

This field specifies the types of transfers that can be requested for this VSAMProfile:

U Uploads from the PC to the Host.D Downloads from the Host to the PCB Both Uploads and Downloads (the default)

(Only Downloads are supported if a Script has been specified.)

CLUSTER / UCAT

These fields can be specified for any Profile with a DATASET name that beginswith 'BIM$'. BIM-PC/TRANSFER will automatically generate a DLBL/DD forthis Cluster and UCAT prior to opening the dataset. If these fields are specified,the Cluster name cannot be specified at the PC.

The UCAT field is only present in VSE.

START KEY

The four lines following this field are used to enter the starting key to be used fora download. A CICS STARTBR GTEQ will be issued using this key. If the actualkeylength of the VSAM dataset is greater than 64 bytes, the remaining keyfieldwill be padded on the right with low-values.

The keyfield can be entered in either character or hexadecimal. The screenpositions following the 1-32 and 33-64 contain the character data (non-printablecharacters are translated to a “.”). The screen positions following the “HEX” linescontain the hexadecimal equivalent of the character line.

You can enter values into both the character and the hexadecimal sections,however, the character entries override the hexadecimal entries.

END KEY

The four lines following this field are used to enter the last key to be used for adownload. The LENGTH field is used to specify how many of the 64 positionsare to be compared to the actual VSAM keyfield for a match. The download willstop when a VSAM key is found that is greater than the value specified here.


Host Customization (SAM Profiles) Page 209

SAM Profile List

The following screen is displayed when the “SAM PROFILE LIST” entry isselected on the System Menu:

*** BIM-PC/TRANSFER *** SAM PROFILE LIST yyyy/mm/dd hh:mm:ss

CMD PROFILE DESCRIPTION DATASET --- ---------------- ---------------------------------------- -------- _ EPICFIX EPIC Type fixed _ EPICUNDEF EPIC Type Undefined _ EPICVAR EPIC Type Variable _ SJAFIXBLK DLBL Type fixed SJASDFB _ SJAUNDEF DLBL Type Undefined SJASDUD _ SJAVARBLK DLBL Type Variable SJASDVB


This screen is used to scroll through all of the “SAM Profiles” that have beendefined to BIM-PC/TRANSFER.



If you have more profiles than can be displayed on a single screen, press PF8 toscroll through the available entries. When the last screen of entries has beendisplayed, pressing PF8 will resume from the first entry.



Page 210 (SAM Profiles) Host Customization

SAM Profile Definition Screen

The following screen is displayed when the “SAM PROFILE DEFINITIONS”entry is selected on the System Menu, or when an entry is selected from the“SAM PROFILE LIST” screen:

*** BIM-PC/TRANSFER *** SAM PROFILE DEFINITIONS yyyy/mm/dd hh:mm:ss

PROFILE: ________________ DESC: ________________________________________

SECGRP: ________ E(X)IT/(S)CRIPT: _ NAME: ________________ TRANSLATE: * CRLF: * DLBL: _______ OR BIM-EPIC DSN: ____________________________________________

TYPES: D (U)PLOADS, (D)OWNLOADS, (B)OTH

RECFORM: F (F)IXED, (V)ARIABLE, (U)NDEFINED RECSIZE: 00000 (REQUIRED FOR RECFORM=F DATASETS) BLKSIZE: 00000 (REQUIRED FOR UPLOADS)

UPLOAD PROCESSING OPTIONS DOWNLOAD PROCESSING OPTIONS . TRUNCATE LONG RECORDS: N . TRUNCATE TRAILING BLANKS: N . PAD SHORT RECORDS: Y . HEX PAD CHARACTER: 40

DATASET NAME FROM CURRENT DLBL: *** DLBL NOT FOUND ***

MAKE DESIRED CHANGES AND PRESS PF2 TO UPDATE, PF5 TO ADD PF2=UPDATE, PF3=END, PF4=RETURN, PF5=ADD, PF7=PREV, PF8=NEXT, PF12=DELETE

This screen is used to add, update or delete “SAM Profile Definitions”. Refer tothe section “Adding / Changing Definitions” on page 187 of this chapter forgeneral information about the use of this screen.

SAM Profiles are only used in VSE. They are not present in MVS.

SAM Profiles are required in BIM-PC/TRANSFER to perform SAM and/or BIM-EPIC dataset transfers using driver BIMFTRDF in its" SAM" processing mode.They are not used by driver BIMFTRDF when in its "EPIC" processing mode.Refer to the section on driver BIMFTRDF for more information on its twoprocessing modes.

The PC requests a SAM transfer using driver BIMFTRDF by specifying aCATEGORY name and a SAM PROFILE name.

The SAM Profile provides either the DLBL name of a SAM dataset or the datasetname of a BIM-EPIC dataset, the name of any formatting exit or script required,whether uploads and/or downloads are supported for the dataset, and variousother processing options for uploads and downloads.

Key Fields

SAM Profiles are keyed by PROFILE name. Only one SAM Profile can exist withthe same PROFILE name.



PROFILE

This is an internal name assigned by you. Typically the name should representthe type of data being transferred.


DESC

This is displayed on the PC when inquires are requested for available SAMprofiles.

SECGRP

This is a name assigned by you if you wish to restrict the use of this ProfileDefinition to specific PC users.


E(X)IT/(S)CRIPT

This field is used to designate whether or not a “Download Script” or a“formatting/selection exit” is to be used. Refer to the NAME field for additionalinformation:S A script is to be used. The name of the “Download Script” is in the NAME

field.X A formatting/selection exit is to be used. The name of the exit is in the

NAME field.N Neither a script nor an exit is to be used.

NAME

This is the name of the script or formatting / selection exit to be used fortransfers.

An exit is required for all uploads unless The data from the PC is separated intorecords with CRLF’s.

An exit or script is only required for downloads if you wish to filter out selectedrecords, or to change the record formats prior to sending them to the PC.

Script names must match an existing “Download Script Definition” in the HostControl File. Only downloads are supported for scripts.

Exit names must match an existing program defined to CICS. Any namespecified here will override the EXIT specification of the “Category Definition”.Refer to the section “Format / Selection Exits” on page 383 for more information.



TRANSLATE


* Let the DRIVER determine the option.Y For uploads to the host, the incoming data will be translated from ASCII to

EBCDIC. For downloads to the PC, the data will be translated fromEBCDIC to ASCII.


A value of “Y” or “N” will override any specification in the “CategoryDefinition”. Refer to the section on each DRIVER's considerations starting onpage 306 of this manual for more information on the TRANSLATE option.

CRLF


* Let the DRIVER determine the option.Y For uploads to the host, the data has CRLF's separating each record. For

downloads to the PC, each record will be separated by a CRLF.N The records are not separated by CRLF's. Use the LRECL specified by the

PC, or the default LRECL determined by the DRIVER to separate the inputinto records during an upload.

A value of “Y” or “N” will override any specification in the “CategoryDefinition”. Refer to the section on each DRIVER's considerations starting onpage 306 of this manual for more information on the CRLF option.

DLBL

This is the DLBL name of the SAM dataset to be used for the transfer. You mustprovide DLBL and EXTENTs in either the CICS or BIM-TMAN JCL, or standardlabels. You must also ensure that the volumes referenced in the EXTENTs areassigned in the partition running BIM-PC/TRANSFER. This field is required forall SAM profiles unless the "BIM-EPIC DSN" field is used.

BIM-EPIC DSN

This is the dataset name of the BIM-EPIC managed dataset to be used for thetransfer. You must not provide DLBL and EXTENTs for this dataset, BIM-PC/TRANSFER will dynamically generate a DLBL for the duration of thetransfer. This field and the DLBL field are mutually exclusive, only one of themcan be specified.

TYPES

This field specifies the types of transfers that can be requested for this SAMProfile:

U Uploads from the PC to the Host.



D Downloads from the Host to the PC.B Both Uploads and Downloads (the default).

(Only Downloads are supported if a Script has been specified.)

RECFORM

This field specifies the record format of the dataset:

F The dataset contains fixed length blocked or unblocked records.V The dataset contains variable length records in a standard llbb format.U The dataset format is undefined. Each physical block in the dataset will

be treated as a logical record.

RECSIZE

This field specifies the logical record size. It is only used for RECFORM=Fdatasets.

BLKSIZE

This field specifies the physical blocksize of the dataset. It is only used foruploads. For RECFORM=V datasets, this is the maximum blocksize allowed forthe dataset. BIM-PC/TRANSFER supports blocksizes up to 32000.

UPLOAD PROCESSING OPTIONS

The fields under this heading are used during uploads from the PC to the host.

TRUNCATE LONG RECORDS

This field specifies what action should occur if a record from the PC exceeds theRECSIZE specified for a fixed length dataset. If 'N' is specified, the transfer isterminated. If 'Y' is specified, the record is truncated.

PAD SHORT RECORDS

This field specifies what action should occur if a record from the PC is shorterthen the RECSIZE specified for a fixed length dataset. If 'N' is specified, thetransfer is terminated. If 'Y' is specified, the record is padded with the valuespecified for "HEX PAD CHARACTER".

HEX PAD CHARACTER

This field specifies the pad character to be used to pad short records. It isspecified as a two digit hex value. A value of 40 is a space.

DOWNLOAD PROCESSING OPTIONS

The fields under this heading are used during downloads from the host to thePC.



TRUNCATE TRAILING BLANKS

This field specifies whether or not trailing blanks should be truncated from thehost records. This option can be overriden by the PC user when the transfer isrequested.

DATASET NAME FROM CURRENT DLBL

This field displays the dataset name retrieved from the DLBL specified in theDLBL field. Verify that this is the desired dataset.


Host Customization (Download/HOSTAFT Scripts) Page 215

Script Definitions List

The following screen is displayed when the “SCRIPT DEFINITIONS LIST” entryis selected on the System Menu:

*** BIM-PC/TRANSFER *** SCRIPT DEFINITIONS LIST yyyy/mm/dd hh:mm:ss

CMD SCRIPT NAME DESCRIPTION --- ---------------- ---------------------------------------- _ SampleScript1 Sample Script Description _ SampleScript2 Sample Script Description _ SampleScript3 Sample Script Description


This screen is used to scroll through all of the “Download Scripts” and“HOSTAFT Scripts” that have been defined or uploaded to BIM-PC/TRANSFER.



If you have more scripts than can be displayed on a single screen, press PF8 toscroll through the available entries. When the last screen of entries has beendisplayed, pressing PF8 will resume from the first entry.



Page 216 (Download/HOSTAFT Scripts) Host Customization

Script Definition Screen

The following screen is displayed when the “SCRIPT DEFINITIONS” entry isselected on the System Menu, or when an entry is selected from the “SCRIPTDEFINITIONS LIST” screen:

*** BIM-PC/TRANSFER *** SCRIPT DEFINITIONS yyyy/mm/dd hh:mm:ss

SCRIPT: ________________ DESC: ________________________________________COMMAND: ______________________________________________________________________ LINE+ 1(11) 0...+....1....+....2....+....3....+....4....+....5....+....6....+....7.. CMD *This is a test script *===* #option ascii=yes,eof=yes,separator=, decimalpt=. *===* #record V 24 139 *===* RECORD-KEY X 0 16 A *===* RECORD-TYPE X 16 1 A *===* #IF RECORD-TYPE = A AddressRec *===* #ERROR Bad Record Type *===* @AddressRec *===* NAME X 17 30 A *===* ADDRESS X 47 30 A *===* #END *===* *---* *---* *---*MAKE DESIRED CHANGES AND PRESS PF2 TO UPDATE, PF5 TO ADDPF2=UPDATE, PF3=END, PF4=RETURN, PF5=ADD, PF7=PREV, PF8=NEXT, PF12=DELETE

This screen is used to add, update or delete “Download Script Definitions” and“HOSTAFT Script Definitions”. Refer to the section “Adding / ChangingDefinitions” on page 187 of this chapter for general information about the use ofthis screen.

Download scripts can be used during all downloads to PCs to perform recordand field selections and output formatting.

For VSAM downloads, the script name can be provided in a “VSAM ProfileDefinition” described earlier in this manual.

For all other downloads, the script name is provided in the “Download SelectionDialog” on the PC. Refer to the sections “Download Selection Dialog” on page 97and "Download Script Name" on page 99 for more information.

HOSTAFT scripts are used by the “Host initiated Automatic File Transfer”feature of BIM-PC/TRANSFER.

Scripts can be defined using this screen, or they can be uploaded from PCs usinga “Category Definition” defined for driver BIMFTRDX.

Refer to the section “File Conversion Scripts” on page 271 for rules on how tocode a download script.

Refer to the section “Automatic Transfer Script” on page 125, and the section“HOSTAFT Script Overview” on page 160, for rules on how to code HOSTAFTscripts.



This screen is basically a full-screen text editor. Several commands are providedfor the COMMAND line to position within the script, or find/change text withinthe script. Each text line contains a “line command area” (CMD) that acceptscommands to insert, move, copy, modify, or delete individual lines within thescript. Lines that are copied or moved are placed in an internal stack area. Thisstack is maintained for the life of the FTRM transaction. This allows lines to becopied or moved from one script definition to another.

Key Fields

Download scripts are keyed by SCRIPT name. Only one script can exist with thesame SCRIPT name.

SCRIPT

This is the name of the script. It is assigned by you, and can be up to 16characters in length. Typically the name should represent the type of data beingtransferred.

DESC

This is displayed on the PC as the title of a #PROMPT dialog box.

COMMAND

This field is used to pass commands to the script full-screen editor. The followingcommands are supported:

TOP Position display to the first screen of script lines.

BOT Position display to the last screen of script lines.

CLS Clear copy/move stack.

NEW Clear all lines of current script.

U nnn Position display towards the top by nnn lines.

D nnn Position display towards the bottom by nnn lines.

P nnn Position display to line nnn.

F /text/

F

Position display to the next line in the scriptcontaining the string /text/. The '/' is a delimiterthat can be any of the following four characters ( '" / \ ) You must use the same delimiter at bothends of the text.

Repeat previous find request.


Page 218 (Download/HOSTAFT Scripts) Host Customization

C /text/newtext/

C

Change the next occurrence of /text/ to/newtext/. The '/' is a delimiter that can be any ofthe following four characters ( ' " / \ )You must use the same delimiter at both ends ofthe text.Repeat previous change request

LINE=nnn(mmm)

This field displays the current position within the script. 'nnn' is the line numberof the first script line being displayed, beginning with 1. 'mmm' is the totalnumber of lines in the script.

CMD

These fields are used to edit the individual lines of the script. Line commands canbe entered in upper or lower case. The following line commands are supported:

Function Line Command Description

move M or Mnn

V Vnn

MM

VV

(nn = number of lines to move)

(move, extend)

(block move)

(block move, extend stack)

copy C or Cnn

K Knn

CC

KK

(nn = number of lines to copy)

(copy, extend stack)

(block copy)

(block copy, extend stack)

delete D or Dnn

DD

(nn = number of lines to delete)

(block delete)

new lines I or Inn (nn = number of new lines to insert)

after A or Ann (nn = number of times to insert stack)

before B or Bnn (nn = number of times to insert stack)

repeat R or Rnn

" or "nn

RR or ""

RR or RRn"" or ""n

(nn = number of times to repeat line)

(nn = number of times to repeat line)

(block repeat, start)

(block repeat, end, n=number of times torepeat block)



shift left < or <nn

<<

<< or <<n

(nn = number of chars to shift left)

(block shift left, start)

(block shift left, end, n= nbr of chars toshift left)

shift right > or >nn

>>

>> or >>n

(nn = number of chars to shift right)

(block shift right, start)

(block shift right, end, n= nbr of chars toshift left)

upper case U or Unn

UU

(nn - nbr of lines to convert)

(block convert)


Page 220 (Dataset Access) Host Customization

Dataset Access List

The following screen is displayed when the “DATASET ACCESS LIST” entry isselected on the System Menu:

*** BIM-PC/TRANSFER *** DATASET ACCESS LIST yyyy/mm/dd hh:mm:ss

CMD NAME DESCRIPTION --- -------- ---------------------------------------- _ CLA1 Dataset Access Record 1 _ CLA2 Dataset Access Record 2


This screen is used to scroll through all of the “Dataset Access Definitions” thathave been defined to BIM-PC/TRANSFER.






Host Customization (Dataset Access) Page 221

Dataset Access Definition Screen

The following screen is displayed when the “DATASET ACCESS DEFINITIONS”entry is selected on the System Menu, or when an entry is selected from the“DATASET ACCESS LIST” screen:

*** BIM-PC/TRANSFER *** DATASET ACCESS DEFINITIONS yyyy/mm/dd hh:mm:ss

NAME: ________ DESC: ________________________________________

DATASET NAME MASK SECGRP ============================================ ======== 1 %USER.* __________________________________ ________ 2 BIM.TEST.*__________________________________ ________ 3 PROD.*.FILE_________________________________ PRODGRP 4 TEST.%USER.*________________________________ ________ 5 ____________________________________________ ________ 6 ____________________________________________ ________ 7 ____________________________________________ ________ 8 ____________________________________________ ________ 9 ____________________________________________ ________ 10 ____________________________________________ ________ 11 ____________________________________________ ________ 12 ____________________________________________ ________ 13 ____________________________________________ ________ 14 ____________________________________________ ________ 15 ____________________________________________ ________

MAKE DESIRED CHANGES AND PRESS PF2 TO UPDATE, PF5 TO ADDPF2=UPDATE, 3=END, 4=RETURN, 5=ADD, 7=PREV, 8=NEXT, 10-UP, 11=DN, 12=DELETE

This screen is used to add, update or delete “Dataset Access Definitions”. Referto “Adding / Changing Definitions” on page 187 of this chapter for generalinformation about the use of this screen.

Dataset Access Definitions can be used in BIM-PC/TRANSFER to control thefollowing:

• Access to VSAM datasets by cluster name. Cluster names can be specified fortransfers when using specific VSAM Profiles. Refer to the DATASET field ofthe “VSAM Profile Definition Screen” starting on page 204 for moreinformation. Cluster names are also specified for transfers using driverBIMFTRDC, the VSAM Cluster driver.

• Access to VSE SAM datasets and BIM-EPIC managed datasets.

• Access to MVS Partitioned and QSAM datasets.

You can specify up to 36 dataset names in each definition. If you have moredataset names than will display on a single screen, use PF10 and PF11 to scrollthe current dataset definition list.

Key Fields

Dataset Access Definitions are keyed by NAME.

NAME

This is an internal name assigned by you. Every Dataset Access Definition musthave a unique name.


Page 222 (Dataset Access) Host Customization

This name is then specified in the DATASET ACCESS fields of the UserDefinition and/or VSAM Profile Screens.

DESC

This is for your use to describe the use of each Dataset Access Definition. It isdisplayed on the Dataset Access List Screen.

DATASET NAME MASK

These fields are used to define the VSAM Cluster names, VSE SAM datasetnames, BIM-EPIC managed datasets, Partitioned datasets, and QSAM datasetsthat are valid for this Dataset Access Definition.

PC users that have this Dataset Access Definition defined in their User Definition,or are using a VSAM Profile restricted with this Dataset Access Definition, canonly transfer datasets whose names are defined here.

These fields are generic masks that are used to validate specific dataset namesthat are entered by the PC user for individual transfer requests. These maskfields can contain an '*' to represent a match of 'any number of characters' or a '?'to represent a match of 'any single character'.

You can also specify 'variable names' as part of a Dataset Name Mask. Variablesare replaced by specific data during the validation process. The followingvariables can be specified:

%USER The current PC USER ID.%CATN The current BIM-PC/TRANSFER Category Name.%LIBQ The current BIM-PC/TRANSFER LIBQUE.%DRVD The contents of driver data field 12 from the BIM-PC/TRANSFER

Category being used for the transfer.

The data from each variable is striped of all trailing blanks and inserted into themask.

The Dataset Name Mask fields are maintained in ascending EBCDIC sequence.To remove a mask from list, either erase the field, or key blanks over the nameand press enter. To add a new mask, key the mask into a blank field. It willautomatically be sequenced with the other mask fields.

SECGRP

These fields can be used if you wish to restrict the use of specific dataset masks tospecific PC users.

If a value is specified here, then any user that has a “User Definition” must havethe same value listed in the GROUPS section of the User Definition, or thetransfer request will be rejected by BIM-PC/TRANSFER. See page 202 for moreinformation.


Host Customization (Access Security) Page 223

Access Security Definitions

Access Security Definitions can be used to restrict uploads and/or downloads forspecific Categories and Users.

Each Access security definition contains an array of entries that describe therequirements and restrictions for uploads and/or downloads. Each definition isdefined with a 3-part key:

1) Access Security Group name (CATGRP)

This name can be used to group access definitions for a particulardepartment or group in your company. The Category Definition screencontains a field called "ACCESS SECURITY GROUP". That field is used toenter the Access Security Group name of the access definitions to be usedfor each category.

2) Access Security Type (TYPE)

Each Access Security Definition applies to a specific type of transfer. EachAccess Security Group can contain definitions for any number of types. Thecurrently supported types are:

EDIT BIM-EDIT TransfersPOWER VSE/POWER TransfersLIBR VSE/LIBR TransfersICCF VSE/ICCF DownloadsJES MVS/JES TransfersSCRIPT BIM-PC/TRANSFER Script TransfersTEMPSTG CICS Temporary Storage Transfers

Security for VSAM, PDS and QSAM datasets is provided using DatasetAccess Definitions described on page 221.

3) User Security Group name (SECGRP)

This name can be used to restrict specific Access Security Definitions tousers that are defined with access to a specified SECGRP. See page 202 formore information. Each Access Security Group can have one definition witha blank Security Group for each type. These definitions are assumed to beauthorized for all users.

Access Level and Array Entries

Each array entry in an Access Security Definition contains an Access Level (LVL)that defines the scope of the entry. The following values can be specified:

D the entry defines criteria that applies to downloads only.U the entry defines criteria that applies to uploads only.I the entry is temporarily inactive.N the entry defines criteria to be excluded from all transfers.A the entry defines criteria to be included for all transfers.


Page 224 (Access Security) Host Customization

Each array entry in an Access Security Definition also contains a sequencenumber (SEQ) that is used to maintain the proper sequence of the access tests.

The remainder of each array entry contains the criteria to be matched against therequested upload and/or download. This criteria varies by category type, and isdefined in detail in the following sections.


Every field in each array entry that can allow at least four characters to beentered, can contain one or more of the following variables. The variables aresubstituted at processing time for the actual data they represent:

%NETN VTAM network name of the PC being used for the transfer.%PCUS User id that was entered for the PC signon to BIM-PC/TRANSFER.%USER The user id defined in the User Definition for the current transfer

category. If none specified, this will be the same as %PCUS.%NN Same as %NETN.%US Same as %USER.%PU Same as %PCUS.

Generic Masks

Every field in each array entry is assumed to be a "Generic Mask" that will beused to match to specific category items such as a report name. The followingtable lists each of the generic characters that can be specified along with adefinition if its use.

MaskCode Meaning* Any number of any character+ Any single character@ Any single Alpha (A-Z)# Any single Numeric (0-9)& Any single Alphanumeric (A-Z,0-9)! Any single special character? Any single non-blank printable character> Any number of the following character or mask code¬ 'not' a match for the following character or mask code% The following mask code should be treated as a

character| 'or' the match with the next character or mask code

Processing Overview

When a transfer is requested using a Category Definition that contains an AccessSecurity Group name, the Access Security Definition(s) for the specified groupname and transfer category type are accessed and placed in an incore table. If



more than one Access Security definition is defined for a type within a group,they will be processed in sequence by SECGRP name.

Upload Processing

When an upload is requested, each array entry containing an Access level (LVL)of "U", "A", or "N" is checked until the first entry is found whose criteria matchesthe upload being attempted. Depending on the (LVL) the following action willresult:

U upload will be allowed.A upload will be allowed.N upload will be rejected.

Download Processing

When a download is requested, the first step is to generate a list of availableitems to be sent to the PC. As this list is being generated, each entry in the list ispassed through access security. Each Access Security array entry containing anAccess level (LVL) of "D", "A", or "N" is checked until the first entry is foundwhose criteria matches the available item. Depending on the (LVL) the followingaction will result:

D the available item will be presented to the PC userA the available item will be presented to the PC userN the available item will not be presented to the PC user

When the PC user selects an available item to be downloaded, a second accesssecurity check is made. This is done to catch changes to Access Securitydefinitions between the time of the original query and the actual downloadrequest.



Processing Example

For this example, we will use a subset of the POWER access criteria. The actualcriteria varies by category type and is defined in detail in the following sections.

Assume that an Access Security Definition has been defined for the POWERcategory with the following entries:

SEQ LVL QUE JOBNAME CDP USER INFO=== === === ======== === ===============010 N ___ PROD*___ ___ _______________020 U RDR %USER*__ ___ *%USER*________030 U LST ________ ___ _______________040 D LST ________ Q__ _______________050 B LST %USER*__ ___ _______________060 B LST ________ ___ *%USER*________

SEQ

010 This entry causes all transfers to be rejected to any POWER queue if thejobname begins with "PROD". Entries like this will normally need to bespecified at the beginning of the definition.

020 This entry allows uploads to the RDR queue if the jobname begins withthe PC's user id, and the user info field of the job card contains the PC'suser id.

030 This entry allows all uploads to the LST queue.

040 This entry allows downloads from the LST queue only from class Q.

050 This entry allows uploads and downloads to and from the LST queue forany report that begins with the PC's user id. In this example, however,this entry will only be examined for download requests, because entry030 will be 'matched' first for all uploads to the LST queue.

060 This entry allows uploads and downloads to and from the LST queue forany report that contains the PC's user id in the user information field.

All transfers involving the PUN queue will be rejected in this example because noaccess has be specified. In addition, all transfers that do not meet one of these sixentries will be rejected.



Access Security Definitions (List)

The following screen is displayed when the “DATASET ACCESS DEFINITIONS”entry is selected on the System Menu:

*** BIM-PC/TRANSFER *** ACCESS SECURITY DEFINITIONS yyyy/mm/dd hh:mm:ss

CMD CATGRP TYPE SECGRP DESCRIPTION --- -------- -------- -------- ---------------------------------------- _ GROUP1 EDIT Common EDIT Access Rules _ GROUP1 EDIT SECGRP1 EDIT Access Rules For SECGRP1 _ GROUP1 EDIT SECGRP2 EDIT Access Rules For SECGRP2 _ GROUP1 ICCF ICCF Access Rules _ GROUP1 JES JES Access Rules _ GROUP1 LIBR LIBR Access Rules _ GROUP1 POWER POWER Access Rules _ GROUP1 SCRIPT SCRIPT Access Rules

CMD VALUES ARE: (S)ELECT, (D)ELETE PF2=NEW, PF3=END, PF4=RETURN, PF8=SCROLL

This screen is used to review the “Access Security Definitions” that have beendefined to BIM-PC/TRANSFER, and to add new Access Security Definitions.



If you have more definitions than can be displayed on a single screen, press PF8to scroll through the available entries. When the last screen of entries has beendisplayed, pressing PF8 will go back to the first entry.

PF2 is used to add new Access Security Definitions. When you press PF2, a menuof Access Security Types will be displayed. Select the type you want to add, andpress enter. A blank entry of the selected type will then be displayed. Key in therequired information for the new entry, and press PF5 to add the new entry. Youcan cancel out of the add process at any time by pressing PF3, PF4, or CLEAR.




Access Security Definitions for POWER

The following screen is displayed when a POWER entry is selected from the“ACCESS SECURITY DEFINITIONS” list screen, or when scrolling through yourAccess Security Definitions, and a POWER entry is reached:


CATGRP: GROUP1__ TYPE: POWER ACCESS DEFINITION SECGRP: ________ DESC: Sample POWER Access Definition__________ <=MORE=> SEQ LVL QUE JOBNAME CDP DESTNODE DESTUSER ORIGNODE ORIGUSER USER INFO FORM S === === === ======== === ======== ======== ======== ======== ================ ==== = 010 N RDR ________ ___ ________ ________ ________ ________ ________________ ____ _ 020 N LST ________ _H_ ________ ________ ________ ________ ________________ ____ _ 030 N PUN ________ ___ ________ ________ ________ ________ ________________ ____ _ 040 N LST ________ ___ ________ ________ ________ ________ ________________ ____ _ 050 N LST ________ ___ ________ ________ ________ MB______ ________________ ____ _ 060 D LST ________ ___ ________ R029____ ________ ________ ________________ ____ _ 070 D LST ________ ___ ________ ________ ________ ________ *%USER*_________ ____ _ 080 D LST *CICS*__ ___ ________ ________ ________ ________ ________________ ____ _ 090 _ ___ ________ ___ ________ ________ ________ ________ ________________ ____ _ 100 _ ___ ________ ___ ________ ________ ________ ________ ________________ ____ _ 110 _ ___ ________ ___ ________ ________ ________ ________ ________________ ____ _ 120 _ ___ ________ ___ ________ ________ ________ ________ ________________ ____ _ 130 _ ___ ________ ___ ________ ________ ________ ________ ________________ ____ _ 140 _ ___ ________ ___ ________ ________ ________ ________ ________________ ____ _ 150 _ ___ ________ ___ ________ ________ ________ ________ ________________ ____ _ MAKE DESIRED CHANGES AND PRESS PF2 TO UPDATE, PF5 TO ADD F2=UPD, 3=END, 4=RTN, 5=ADD, 6=(<), 7=PRE, 8=NXT, 9 =(>), 10=UP, 11=DN, 12=DEL

This screen is used to add, update or delete “Access Security Definitions” forPOWER category types. Refer to “Adding / Changing Definitions” on page 187of this chapter for general information about the use of this screen.

Access Security Definitions can be used to restrict uploads and downloads forspecific Categories and Users.

You can specify up to 35 entries in each POWER definition. Use PF10 and PF11 toscroll through the list of entries.

The screen shown is wider than an actual 3270. On your terminal you will needto use PF6 and PF9 to shift the screen left and right to view all of the fields. The"<=MORE=>" field at the top right edge of the array will keep you informed ofwhat shifting is available.

Common Fields

The following fields appear on the Access Security Definition Screens for allcategory types.

CATGRP

This is an internal name assigned by you. Every Access Security Definition musthave a name. It is part of the key. This name is then specified in the ACCESSSECURITY GROUP field of the Category Definition Screen.



TYPE

This field is provided by BIM-PC/TRANSFER. It is used to indicate the categorytype that this definition is used for. It is part of the key. Refer to section "AccessSecurity Definitions" on page 223 for more information.

SECGRP

This is an internal name assigned by you. It is part of the key. If specified, thiswill limit the use of this Access Security Definition to only those users thatcontain the same name in the GROUPS field of their User Definition. Refer tosection "Access Security Definitions" on page 223 and the GROUPS field on page202 for more information.

SEQ

This field is used to control the order in which the entries in each Access SecurityDefinition are examined. As you insert/change/delete entries in the array, theentries will automatically be sorted into SEQ order, and then renumbered.

To delete an entry from the array, change its SEQ number to "000".

To add a new entry into the middle of an array, change the SEQ number of anyunused entry at the end of the array to a number that occurs between the twoentries you want the new entry to appear.

LVL

This field defines the scope of each array entry. The following values can bespecified:

D the entry defines criteria that applies to downloads only.U the entry defines criteria that applies to uploads only.I the entry is temporarily inactive.N the entry defines criteria to be excluded from all transfers.A the entry defines criteria to be included for all transfers.

If you set the LVL field to a space, and it is the last used entry in the array, it willautomatically be deleted when the definition is updated.

Refer to section "Processing Overview" on page 224 for more information.



Array Fields for POWER

The following fields are unique to POWER Access Security Definitions.

QUE POWER Queue (LST, RDR, PUN).

JOBNAME Job name of entry in queue.

CDP POWER class, disposition and priority.

DESTNODE Destination node name.

DESTUSER Destination user id.

ORIGNODE Origination node name.

ORIGUSER Origination user id.

USER INFO USER= field of the * $$ JOB statement.

FORM Forms id.

S POWER System id (1-9).



Access Security Definitions for EDIT

The following screen is displayed when an EDIT entry is selected from the“ACCESS SECURITY DEFINITIONS” list screen, or when scrolling through yourAccess Security Definitions, and an EDIT entry is reached:


CATGRP: GROUP1__ TYPE: EDIT ACCESS DEFINITION SECGRP: ________ DESC: Sample_EDIT_Access_Definition___________ MORE=> SEQ LVL LIBRARY NAME MEMBER NAME TYPE ATTR TITLE/DESCRIPTION === === ================ ================ ======== ======== =================== 010 D BIM*____________ ________________ ________ ________ ___________________ 020 A %USER___________ ________________ ________ ________ ___________________ 030 _ ________________ ________________ ________ ________ ___________________ 040 _ ________________ ________________ ________ ________ ___________________ 050 _ ________________ ________________ ________ ________ ___________________ 060 _ ________________ ________________ ________ ________ ___________________ 070 _ ________________ ________________ ________ ________ ___________________ 080 _ ________________ ________________ ________ ________ ___________________ 090 _ ________________ ________________ ________ ________ ___________________ 100 _ ________________ ________________ ________ ________ ___________________ 110 _ ________________ ________________ ________ ________ ___________________ 120 _ ________________ ________________ ________ ________ ___________________ 130 _ ________________ ________________ ________ ________ ___________________ 140 _ ________________ ________________ ________ ________ ___________________ 150 _ ________________ ________________ ________ ________ ___________________ MAKE DESIRED CHANGES AND PRESS PF2 TO UPDATE, PF5 TO ADD F2=UPD, 3=END, 4=RTN, 5=ADD, 6=(<), 7=PRE, 8=NXT, 9 =(>), 10=UP, 11=DN, 12=DEL

This screen is used to add, update or delete “Access Security Definitions” forEDIT category types. Refer to “Adding / Changing Definitions” on page 187 ofthis chapter for general information about the use of this screen.


You can specify up to 28 entries in each EDIT definition. Use PF10 and PF11 toscroll through the list of entries.

The screen shown is wider than an actual 3270. On your terminal you will needto use PF6 and PF9 to shift the screen left and right to view all of the fields. The"<=MORE=>" field at the top right edge of the array will keep you informed ofwhat shifting is available.

Common Fields

Refer to section "Common Fields" on page 228 for a description of the fields thatare common to all Access Security Definitions.



Array Fields for BIM-EDIT

The following fields are unique to BIM-EDIT Access Security Definitions.

LIBRARY NAME BIM-EDIT Library name.

MEMBER NAME BIM-EDIT Member name.

TYPE BIM-EDIT "TYPE" field for member.

ATTR BIM-EDIT "ATTR" field for member.

TITLE/DESC BIM-EDIT Title/Description field for member.



Access Security Definitions for Scripts

The following screen is displayed when a SCRIPT entry is selected from the“ACCESS SECURITY DEFINITIONS” list screen, or when scrolling through yourAccess Security Definitions, and a SCRIPT entry is reached:


CATGRP: GROUP1__ TYPE: SCRIPT ACCESS DEFINITION SECGRP: ________ DESC: Sample_Script_Access_Definition_________

SEQ LVL SCRIPT NAME TITLE/DESCRIPTION === === ================ ======================================== 010 D HOST*___________ ________________________________________ 020 D ________________ *HOST*__________________________________ 030 B %USER*__________ ________________________________________ 040 _ ________________ ________________________________________ 050 _ ________________ ________________________________________ 060 _ ________________ ________________________________________ 070 _ ________________ ________________________________________ 080 _ ________________ ________________________________________ 090 _ ________________ ________________________________________ 100 _ ________________ ________________________________________ 110 _ ________________ ________________________________________ 120 _ ________________ ________________________________________ 130 _ ________________ ________________________________________ 140 _ ________________ ________________________________________ 150 _ ________________ ________________________________________ MAKE DESIRED CHANGES AND PRESS PF2 TO UPDATE, PF5 TO ADD F2=UPD, 3=END, 4=RTN, 5=ADD, 6=(<), 7=PRE, 8=NXT, 9 =(>), 10=UP, 11=DN, 12=DEL

This screen is used to add, update or delete “Access Security Definitions” forSCRIPT category types. Refer to “Adding / Changing Definitions” on page 187 ofthis chapter for general information about the use of this screen.


SCRIPT definitions are used to control upload/download access to BIM-PC/TRANSFER Script definitions.

You can specify up to 33 entries in each SCRIPT definition. Use PF10 and PF11 toscroll through the list of entries.

Common Fields


Array Fields for BIM-PC/TRANSFER Script Security

The following fields are unique to SCRIPT Access Security Definitions.

SCRIPT NAME Name of the Script.

TITLE/DESC Title/Description field for the script.



Access Security Definitions for ICCF

The following screen is displayed when an ICCF entry is selected from the“ACCESS SECURITY DEFINITIONS” list screen, or when scrolling through yourAccess Security Definitions, and an ICCF entry is reached:


CATGRP: GROUP1__ TYPE: ICCF ACCESS DEFINITION SECGRP: ________ DESC: Sample_ICCF_Definition__________________

SEQ LVL LIB MEMBER USER === === === ======== ==== 010 D 050 COM*____ AAAA 020 D 051 ________ ____ 030 _ ___ ________ ____ 040 _ ___ ________ ____ 050 _ ___ ________ ____ 060 _ ___ ________ ____ 070 _ ___ ________ ____ 080 _ ___ ________ ____ 090 _ ___ ________ ____ 100 _ ___ ________ ____ 110 _ ___ ________ ____ 120 _ ___ ________ ____ 130 _ ___ ________ ____ 140 _ ___ ________ ____ 150 _ ___ ________ ____ MAKE DESIRED CHANGES AND PRESS PF2 TO UPDATE, PF5 TO ADD F2=UPD, 3=END, 4=RTN, 5=ADD, 6=(<), 7=PRE, 8=NXT, 9 =(>), 10=UP, 11=DN, 12=DEL

This screen is used to add, update or delete “Access Security Definitions” forICCF category types. Refer to “Adding / Changing Definitions” on page 187 ofthis chapter for general information about the use of this screen.


ICCF definitions are used to control download access to ICCF libraries and/ormembers.

You can specify up to 50 entries in each ICCF definition. Use PF10 and PF11 toscroll through the list of entries.

Common Fields




Array Fields for ICCF Security

The following fields are unique to ICCF Access Security Definitions.

LIB ICCF library number (3 digits).

MEMBER ICCF member name.

USER ICCF member’s user id.



Access Security Definitions for LIBR

The following screen is displayed when a LIBR entry is selected from the“ACCESS SECURITY DEFINITIONS” list screen, or when scrolling through yourAccess Security Definitions, and a LIBR entry is reached:


CATGRP: GROUP1__ TYPE: LIBR ACCESS DEFINITION SECGRP: ________ DESC: Sample_LIBR_Access_Definition___________

SEQ LVL LIBRARY.SUBLIB MEMBER TYPE === === ================ ======== ======== 010 D BIMLIB.*________ B*______ ________ 020 D BIMLIB.*________ %USER*__ ________ 030 U BIMLIB.T________ %USER*__ A_______ 040 U BIMLIB.T________ %USER*__ C_______ 050 _ ________________ ________ ________ 060 _ ________________ ________ ________ 070 _ ________________ ________ ________ 080 _ ________________ ________ ________ 090 _ ________________ ________ ________ 100 _ ________________ ________ ________ 110 _ ________________ ________ ________ 120 _ ________________ ________ ________ 130 _ ________________ ________ ________ 140 _ ________________ ________ ________ 150 _ ________________ ________ ________ MAKE DESIRED CHANGES AND PRESS PF2 TO UPDATE, PF5 TO ADD F2=UPD, 3=END, 4=RTN, 5=ADD, 6=(<), 7=PRE, 8=NXT, 9 =(>), 10=UP, 11=DN, 12=DEL

This screen is used to add, update or delete “Access Security Definitions” forLIBR category types. Refer to “Adding / Changing Definitions” on page 187 ofthis chapter for general information about the use of this screen.


LIBR definitions are used to control upload/download access to VSE LIBRlibraries, sublibraries and/or members.

You can specify up to 50 entries in each LIBR definition. Use PF10 and PF11 toscroll through the list of entries.

Common Fields




Array Fields for VSE LIBR Security

The following fields are unique to LIBR Access Security Definitions.

LIBRARY.SUBLIB LIBR Library.Sublibrary name.

MEMBER LIBR member name.

TYPE LIBR member type (A, C, etc.)



Access Security Definitions for JES

The following screen is displayed when a JES entry is selected from the “ACCESSSECURITY DEFINITIONS” list screen, or when scrolling through your AccessSecurity Definitions, and a JES entry is reached:


CATGRP: GROUP1__ TYPE: JES ACCESS DEFINITION SECGRP: ________ DESC: Sample_JES_Access_Definition____________

SEQ LVL Q JOBNAME CL JID GROUPID OWNER DEST PROGRAMMER === === = ======== == === ======== ======== ======== ==================== 010 D _ %USER*__ _ ___ ________ ________ ________ ____________________ 020 D _ ________ _ ___ ________ ________ ________ *%USER*_____________ 030 U _ ________ _ ___ ________ ________ ________ ____________________ 040 _ _ ________ _ ___ ________ ________ ________ ____________________ 050 _ _ ________ _ ___ ________ ________ ________ ____________________ 060 _ _ ________ _ ___ ________ ________ ________ ____________________ 070 _ _ ________ _ ___ ________ ________ ________ ____________________ 080 _ _ ________ _ ___ ________ ________ ________ ____________________ 090 _ _ ________ _ ___ ________ ________ ________ ____________________ 100 _ _ ________ _ ___ ________ ________ ________ ____________________ 110 _ _ ________ _ ___ ________ ________ ________ ____________________ 120 _ _ ________ _ ___ ________ ________ ________ ____________________ 130 _ _ ________ _ ___ ________ ________ ________ ____________________ 140 _ _ ________ _ ___ ________ ________ ________ ____________________ 150 _ _ ________ _ ___ ________ ________ ________ ____________________ MAKE DESIRED CHANGES AND PRESS PF2 TO UPDATE, PF5 TO ADD F2=UPD, 3=END, 4=RTN, 5=ADD, 6=(<), 7=PRE, 8=NXT, 9 =(>), 10=UP, 11=DN, 12=DEL

This screen is used to add, update or delete “Access Security Definitions” for JEScategory types. Refer to “Adding / Changing Definitions” on page 187 of thischapter for general information about the use of this screen.


JES definitions are used to control download access to JES queue entries.

Uploads to the JES internal reader can be only be allowed or disallowed by thepresence or absence of an array entry with a LVL of 'U'. All other fields in anarray entry are ignored for uploads.

You can specify up to 35 entries in each JES definition. Use PF10 and PF11 toscroll through the list of entries.

Common Fields




Array Fields for JES Security

The following fields are unique to JES Access Security Definitions.

Q JES queue. I=Internal reader (uploads)O=Output (downloads)H=Held (downloads)

JOBNAME Job/Report name in Output/Held queues.

CL Job/Report output class.

JID Job ID type (STC, JOB, TSU).

GROUPID JES Output Group.

OWNER TSO Userid that submitted the report.

DEST Destination for the report. (LOCAL, Un, Rn)

PROGRAMMER Programmer field from the JOB statement.



Access Security Definitions for CICS Temporary Storage

The following screen is displayed when a TEMPSTG entry is selected from the“ACCESS SECURITY DEFINITIONS” list screen, or when scrolling through yourAccess Security Definitions, and a TEMPSTG entry is reached:


CATGRP: GROUP1__ TYPE: TEMPORARY STORAGE DEFINITION SECGRP: ________ DESC: Sample_Temp_Stg_Access_Definitions______

SEQ LVL TS QUEUE SYS STG PUR === === ======== ==== ==== === 010 U PC*_____ TEST AUX_ ___ 020 D PC*_____ ____ ____ NO_ 030 D ________ ____ ____ NO_ 040 _ ________ ____ ____ ___ 050 _ ________ ____ ____ ___ 060 _ ________ ____ ____ ___ 070 _ ________ ____ ____ ___ 080 _ ________ ____ ____ ___ 090 _ ________ ____ ____ ___ 100 _ ________ ____ ____ ___ 110 _ ________ ____ ____ ___ 120 _ ________ ____ ____ ___ 130 _ ________ ____ ____ ___ 140 _ ________ ____ ____ ___ 150 _ ________ ____ ____ ___ MAKE DESIRED CHANGES AND PRESS PF2 TO UPDATE, PF5 TO ADD F2=UPD, 3=END, 4=RTN, 5=ADD, 6=(<), 7=PRE, 8=NXT, 9 =(>), 10=UP, 11=DN, 12=DEL

This screen is used to add, update or delete “Access Security Definitions” forCICS Temporary Storage category types. Refer to “Adding / ChangingDefinitions” on page 187 of this chapter for general information about the use ofthis screen.


You can specify up to 50 entries in each TEMPSTG definition. Use PF10 and PF11to scroll through the list of entries.

Common Fields




Array Fields for CICS Temporary Storage Security

The following fields are unique to TEMPSTG Access Security Definitions.

TS QUEUE CICS Temporary Storage queue name.

SYS CICS SYSID of the system owning the queue.

STG AUX/MAIN. Can be used to restrict uploads to aspecific type. This field can only be specified fordefinitions with a LVL of 'U'.

PUR YES/NO/*. Can be used on downloads to controlwhether or not the purge option can be used.


Page 242 (HOSTAFT Status) Host Customization

HOSTAFT Status List

The following screen is displayed when the “HOSTAFT STATUS LIST” entry isselected on the System Menu:

*** BIM-PC/TRANSFER *** HOSTAFT STATUS LIST yyyy/mm/dd hh:mm:ss

CMD DATE TIME SCRIPT JOBNAME TRANSFER STATUS --- ---------- -------- ---------------- -------- ---------------- _ 1996/01/02 13:26:34 HOST SCRIPT 5 TESTJOB5 INCOMPLETE _ 1996/01/02 08:18:16 HOST SCRIPT 4 TESTJOB4 COMPLETED OK _ 1995/12/13 10:27:26 HOST SCRIPT 4 TESTJOB4 COMPLETED OK _ 1995/12/11 12:26:38 HOST3 JOB3 ERRORS OCCURRED _ 1995/12/11 10:04:00 HOST4 JOB4 COMPLETED OK _ 1995/12/11 10:56:38 HOST2 JOBTWO ERRORS OCCURRED


This screen is used to scroll through all of the HOSTAFT scripts that have beenactivated for processing and are either:

• waiting for one or more PC’s to request or complete their script processing,

• have been completed and either had processing errors that need review,

• or contained the #KEEP statement that maintains the status record untilmanually deleted.

The entries are displayed in date/time sequence, with the newest entries first.The Transfer Status field will be one of the following:

COMPLETED OK all PC’s have completed their processing without errorINCOMPLETE some but not all of the PC’s have completed their

processingERRORS OCCURRED all PC’s have completed their processing, but at least

one of them had an error

You can display the detail for a specific HOSTAFT request by entering 'S' in theCMD line for a desired entry and pressing ENTER. If no lines contain an 'S', theline containing the cursor will be selected.

You can delete unneeded entries by entering 'D' in the CMD line(s) for the entriesto be deleted and pressing ENTER. If you delete an entry while a PC isprocessing it, an error will be generated at the PC when it completes.

If you have more entries than can be displayed on a single screen, press PF8 toscroll through the available entries. When the last screen of entries has beendisplayed, pressing PF8 will resume from the first entry.


Host Customization (HOSTAFT Status) Page 243




HOSTAFT Status Detail Screen

The following screen is displayed when the “HOSTAFT STATUS DETAIL” entryis selected on the System Menu, or when an entry is selected from the“HOSTAFT STATUS LIST” screen:

*** BIM-PC/TRANSFER *** HOSTAFT STATUS DETAIL yyyy/mm/dd hh:mm:ss

SCRIPT: HOST SCRIPT 5 JOBNAME: TESTJOB5 START: 1996/01/02 13:26:34 STATUS: INCOMPLETE LAST: 1996/01/02 13:48:21 UPARMS: ________ ________ ________ ________ #KEEP: N ________ ________ ________ ________

CMD NETNAME NETNAME STATUS DATE TIME === ======== ============================== ========== ======== 1 _ PCLU01 WAITING FOR PC QUERY 2 _ PCLU02 SCRIPT SENT TO PC 1996/01/02 13:45:10 3 _ PCLU03 SCRIPT ERROR 1996/01/02 13:48:21 4 _ PCLU04 TRANSFER ERROR 1996/01/02 13:40:05

CMD VALUES ARE: (A)DD, (D)ELETE, (R)ESET STATUS, (V)IEW LOGPF2=UPD, 3=END,4=RTN,5=SCRIPT,6=TOP,7=PREV,8=NEXT,9=BOT,10=UP,11=DN,12=DEL

This screen is used to view, update or delete HOSTAFT script status entries.

Each time a HOSTAFT script is activated, a new status entry is added to the BIM-PC/TRANSFER Host Control File. These entries are used by the host system tomonitor the progress of the processing by each PC defined in the script. When allPC’s have successfully completed processing, the status entry is deleted. If thescript contains the #KEEP statement, the entry is not deleted until someone doesso using this display.

Special PF Keys

There are two PF keys unique to this screen:

PF5 Pressing this PF key will display the contents of the HOSTAFT Scriptused for this status entry. When you have completed viewing thescript, press PF4 to return to this screen.

PF12 Pressing this PF key will delete the current status entry.Once deleted, it cannot be un-deleted.

General Script Information Fields

The fields on the top few lines of the screen display information about the script:script name, jobname,status, uparms, start time and last update time. These fieldsare for display only and cannot be modified.



SCRIPT

Name of the HOSTAFT script.

JOBNAME

Name of the job that activated this HOSTAFT script.

START

Date and time that this HOSTAFT script was activated.

STATUS

Current processing status of displayed script:

COMPLETED OK all PC’s have completed their processing without errorINCOMPLETE some but not all of the PC’s have completed their

processingERRORS OCCURRED all PC’s have completed their processing, but at least

one of them had an error

LAST

Date and time of the last action by a PC for this HOSTAFT script.

UPARMS

These fields contain the eight user parm fields that were specified when the scriptwas activated. User parms are used to replace variables in the HOSTAFT scriptsat activation to provide external control of processing options the script willexecute.

#KEEP

This field indicates, (Y/N), whether or not the script contained the #KEEPstatement. The HOSTAFT status entries for scripts containing this statement willnot be deleted upon successful completion. They will remain in the Host Controlfile until manually deleted using this display.

Individual PC Status Fields

The list of entries in the main body of the screen contains a line for the netnameof each PC workstation defined in the HOSTAFT script in #SENDTO statements.If the script contains more PC’s than will display on one screen, use PF10 andPF11 to scroll the list.

CMD

The following commands/actions can be performed against individual PCnetname entries:



A Add a new PC netname entry to the active script. Enter the “A” CMD on anyexisting line and press ENTER. You will then be prompted to enter theVTAM netname of the PC workstation to be added. Enter the netname at thelocation of the cursor and press ENTER. A new line will appear inNETNAME sequence with a status of “WAITING FOR PC QUERY”.

D Delete a PC netname entry from the active script. If you delete an entry for aPC workstation that is currently processing the script, an error will bereported at the PC when its processing has been completed.

R Reset PC status. This command will reset the status to “WAITING FOR PCQUERY” which will cause this script to be resent to the PC workstation thenext time it inquires for work.

V View Error Log. If the status for this PC workstation indicates an error hasoccurred, this command can be used to view the error log returned by thePC describing the exact error condition.

NETNAME

The VTAM netname for the PC workstation. This is also known in VTAM as theLU name. If the “A” CMD is entered. This field will become un-protected and hi-lighted to allow the entry of a new netname.

NETNAME STATUS

These fields contain the status of the processing for each PC workstation definedin the script:

WAITING FOR PC QUERY

The workstation has not yet queried the host for pending work to beperformed. If this status remains too long, check the status of the PCworkstation.

SCRIPT SENT TO PC

The script has been sent to the PC workstation, but the PC has not yetinformed the host that it has completed processing for the script. If thisstatus remains too long, check the status of the PC workstation.

COMPLETED OK

The PC workstation has successfully completed processing for this script.

TRANSFER ERROR

The PC workstation has reported an error during one or more of thetransfers defined in the script. View the PC error log by using the “V”CMD to determine the exact cause of the error.



SCRIPT ERROR

The PC has reported an error in the script statement syntax. View the PCerror log by using the “V” CMD to determine the exact cause of the error.

DATE / TIME

These fields contain the date and time of the last action reported by the PCworkstation.



HOSTAFT Log Display Screen

The following screen is displayed when you use the “V” CMD for a PCworkstation entry on the “HOSTAFT STATUS DETAIL” screen that has reporteda script or transfer error:

*** BIM-PC/TRANSFER *** HOSTAFT LOG DISPLAY yyyy/mm/dd hh:mm:ss

SCRIPT: HOST SCRIPT 5 NETNAME: PCLU03

0...+....1....+....2....+....3....+....4....+....5....+....6....+....7.. 1 L:2 >#XIGNON FILE=D:\BIMWIN\FTR0\ASIGN.DDW 2 *** Unknown command 3 L:3 >#DXWNLOAD POWER LST JNM=BIMLNKQS,CLS=L,DSP=*, 4 *** Unknown command

PRESS ENTER OR PF8 TO SCROLL THROUGH LOG DATA PF3=END, PF4=RETURN, PF5=SCRIPT, PF6=TOP, PF7=UP, PF8=SCROLL

This screen is used to view the PC error log for HOSTAFT script and transfererrors.

Use PF6, PF7 and PF8 to scroll through the lines of the log.

To view the HOSTAFT script contents, press PF5. You can then use PF4 and PF5to “toggle” between the error log and the script definition.


Host Customization (HOSTAFT Activate Script) Page 249

HOSTAFT Activate Script Screen

The following screen is displayed when the “HOSTAFT ACTIVATE SCRIPT”entry is selected on the System Menu:

*** BIM-PC/TRANSFER *** HOSTAFT ACTIVATE SCRIPT yyyy/mm/dd hh:mm:ss

SCRIPT: ________________

JOBNAME: ________

UPARMS (1-4): ________ ________ ________ ________ (5-8): ________ ________ ________ ________

ENTER REQUIRED INFORMATION AND PRESS ENTER PF3=END, PF4=RETURN

This screen is used to activate a HOSTAFT script for processing. This function isnormally performed by a batch job step. This screen can be used to test newscripts, or to resolve problems.

SCRIPT

This field specifies the name of the HOSTAFT script to be activated. This must bethe name of an existing script contained in the Host Control File.

JOBNAME

This field is optional. If provided, it is recorded and reported with all activityrelated to this script’s activation.

UPARMS

These fields contain eight user parm fields. These are used to replace variables inthe HOSTAFT scripts at activation to provide external control of processingoptions the script will execute.


Page 250 TCP/IP Connection Options

TCP/IP Connection Options

The following screen is displayed when the “TCP/IP CONNECTION OPTIONS”entry is selected on the System Menu:

*** BIM-PC/TRANSFER *** TCP/IP CONNECTION OPTIONS yyyy/mm/dd hh:mm:ss

OPTIONS FOR CONNECTIVITY SYSTEMS:

TCP/IP SYSID: 00

PORT NBR: 04097

TRANID FOR BIMFTRI2: FTRI

TRANID FOR BIMFTRIP: FTRP

MAKE DESIRED CHANGES AND PRESS PF2 PF2=UPDATE, PF3=END, PF4=RETURN

This screen is used to define the processing options used by program BIMFTRIPto activate and control TCP/IP connections with PCs.

These options must be set before attempting to activate program BIMFTRIP. Ifany of these options are changed, you will need to cycle CICS or BIM-TMAN.

The current release of BIM-PC/TRANSFER only supports TCP/IP connectionsusing TCP/IP for VSE from Connectivity Systems.

TCP/IP SYSID

This field specifies the SYSID of the partition in which TCP/IP for VSE isrunning.

PORT NBR

This field specifies the port number that program BIMFTRIP will open. The PCprogram must be configured to use the same value. The default is 4097. Anyvalue from 4096 to 65000 can be specified.

TRANID FOR BIMFTRI2

This field specifies the CICS or BIM-TMAN tranid that has been defined forprogram BIMFTRI2.

TRANID FOR BIMFTRIP

This field specifies the CICS or BIM-TMAN tranid that has been defined forprogram BIMFTRIP.


Viewing The Host Transfer Activity Log Page 251

Viewing The Host Transfer Activity Log (FTRL)BIM-PC/TRANSFER can optionally maintain an Activity Log of all transfers thatare performed. This Activity Log is maintained by the host software in a VSAMRRDS dataset that was defined and initialized during the installation of thisproduct.

This section describes the options available for viewing all or portions of the HostActivity Log. Refer to the section “Printing The Host Transfer Activity Log”starting on page 260 for information on printing the Host Activity Log.

The default CICS transaction id for this display is FTRL. This may have beenchanged during the installation of this product.

The Activity Log processing is activated by setting the option “GENERATEEVENT LOG” to “Y” on the “System Options Screen” which begins on page 191.

The Activity Log is a ‘wrap-around’ file. That means that you define the file tohold a specific number of events. Once that number of events has been logged,the file wraps. From that point on, the Activity Log will contain the most recent‘nnnnn’ transfer events, where ‘nnnnn’ is the number of events that the file wasdefined to hold. Each transfer requires two events, one for the transfer begin, andthe other for the transfer completion.


Page 252 Viewing The Host Transfer Activity Log

PF Key Summary

The following PF keys can be used. The bottom line of the screen shows which PFkeys are active.

PF2=REF Causes the display to be refreshed to the most recenttransfer event

PF3=END Terminates the FTRL transaction and returns to CICSor BIM-TMAN

PF4=RETURN Returns from the “Transfer Event Display” to the“Transfer Activity Log” screen

PF7=BWD Scrolls to the previous transfer event. (new in time)

PF8=FWD Scrolls to the next transfer event. (older in time)

PF10=LEFT Scrolls the Variable Data / Error Message text to theleft

PF11=RIGHT Scrolls the Variable Data / Error Message text to theright

PF12=DETAIL Displays the “Transfer Event Display” for the topevent on the “Transfer Activity Log” display

PF keys 13 - 24 work the same as the corresponding keys 1 - 12.



Transfer Activity Log Display

When you first enter the transaction FTRL, a screen similar to the following willbe displayed. The exact format of this screen will depend on which module 3270you are using, and whether or not the FTRL transaction has been defined to CICSwith alternate screen support:

*** BIM-PC/TRANSFER *** TRANSFER ACTIVITY LOG yyyy/mm/dd hh:mm:ss

USERID: DDW_____ NETNAME: ________ APPLID: ________ CATEGORY: ________ LIBQUE: ____________________________________________ 1(71) MORE=> S USERID ACTN NETNAME MM/DD HH:MM:SS CATEGORY LINE CNT BYTE CNT DURATION - -------- ---- -------- ----- -------- -------- --------- ---------- -------- _ SJJ ERR TR30A 12/17 07:01:06 POWER 5 21,132 00:00:01 SJJ UPLD TR30A 12/17 07:01:05 POWER _ SJA OK TR90A 12/16 11:57:13 EDIT 109 1,975 00:00:01 SJA DNLD TR90A 12/16 11:57:12 EDIT _ SJA OK TR90A 12/16 11:41:29 EDIT 127 2,103 00:00:02 SJA DNLD TR90A 12/16 11:41:27 EDIT _ SJA OK TR90A 12/12 18:24:25 POWER 33 1,841 00:00:01 SJA DNLD TR90A 12/12 18:24:25 POWER _ SJA OK TR90A 12/12 18:23:19 POWER 33 1,874 00:00:01 SJA DNLD TR90A 12/12 18:23:19 POWER _ DDW OK AUTODAVE 12/09 13:00:02 POWER 100 2,544 00:00:02 DDW DNLD AUTODAVE 12/09 13:00:00 POWER _ DDW OK Q006 12/09 07:46:51 LIBR 11 618 00:00:14 DDW DNLD Q006 12/09 07:46:38 LIBR _ DDW OK AUTODAVE 12/09 07:44:19 LIBR 11 617 00:00:16 PRESS PF8 TO SCROLL TO MORE EVENTS PF2=REF PF3=END PF8=FWD PF10=LEFT PF11=RIGHT PF12=DETAIL

3270 Model-2 Screen 1


USERID: DDW_____ NETNAME: ________ APPLID: ________ CATEGORY: ________ LIBQUE: ____________________________________________ 1(71) <=MORE=> S USERID ACTN CHR/SEC LIBQUE LRECL TC - -------- ---- ------- -------------------------------------------- ----- ---- _ SJJ ERR 21,132 LST ** SJJ UPLD LST ** _ SJA OK 1,975 BIM ** SJA DNLD BIM ** _ SJA OK 1,051 BIM ** SJA DNLD BIM ** _ SJA OK 1,841 LST ** SJA DNLD LST ** _ SJA OK 1,874 LST ** SJA DNLD LST ** _ DDW OK 1,272 LST ** DDW DNLD LST ** _ DDW OK 44 BIMLIB.T ** DDW DNLD BIMLIB.T ** _ DDW OK 38 BIMLIB.T ** PRESS PF8 TO SCROLL TO MORE EVENTS PF2=REF PF3=END PF8=FWD PF10=LEFT PF11=RIGHT PF12=DETAIL





USERID: DDW_____ NETNAME: ________ APPLID: ________ CATEGORY: ________ LIBQUE: ____________________________________________ 1(71) <=MORE=> S USERID ACTN R PC PATH - -------- ---- ---- ---------------------------------------------------------- _ SJJ ERR N X:\TEMP\PMSTUFF.TXT SJJ UPLD N X:\TEMP\PMSTUFF.TXT _ SJA OK C:\SHAREDFOLDER\NEWMAST SJA DNLD C:\SHAREDFOLDER\NEWMAST _ SJA OK C:\SHAREDFOLDER\TURNOVER SJA DNLD C:\SHAREDFOLDER\TURNOVER _ SJA OK C:\SHAREDFOLDER\BIMFTR SJA DNLD C:\SHAREDFOLDER\BIMFTR _ SJA OK C:\SHAREDFOLDER\BIMFTR SJA DNLD C:\SHAREDFOLDER\BIMFTR _ DDW OK D:\PR-GROUP.LST DDW DNLD D:\PR-GROUP.LST _ DDW OK D:\PROBS\PHASE\BIMFTRTT.PHA DDW DNLD D:\PROBS\PHASE\BIMFTRTT.PHA _ DDW OK D:\PROBS\PHASE\BIMFTRTT.PHA PRESS PF8 TO SCROLL TO MORE EVENTS PF2=REF PF3=END PF8=FWD PF10=LEFT PF11=RIGHT PF12=DETAIL



USERID: DDW_____ NETNAME: ________ APPLID: ________ CATEGORY: ________ LIBQUE: ____________________________________________ 1(71) <=MORE=> S USERID ACTN APPLID TFR-TYPE CONNECTION HOSTAFT SCRIPT JOBNAME - -------- ---- -------- -------- ------------------ ---------------- -------- _ SJJ ERR BIMCICST MANUAL APPC SJJ UPLD BIMCICST MANUAL APPC _ SJA OK BIMCICST MANUAL APPC SJA DNLD BIMCICST MANUAL APPC _ SJA OK BIMCICST MANUAL APPC SJA DNLD BIMCICST MANUAL APPC _ SJA OK BIMCICST MANUAL APPC SJA DNLD BIMCICST MANUAL APPC _ SJA OK BIMCICST MANUAL APPC SJA DNLD BIMCICST MANUAL APPC _ DDW OK ACBLEFT MANUAL IP=172.17.2.4 DDW DNLD ACBLEFT MANUAL IP=172.17.2.4 _ DDW OK BIMCICST MANUAL LU2 DDW DNLD BIMCICST MANUAL LU2 _ DDW OK ACBLEFT MANUAL IP=172.17.2.4PRESS PF8 TO SCROLL TO MORE EVENTS PF2=REF PF3=END PF8=FWD PF10=LEFT PF11=RIGHT PF12=DETAIL



USERID: DDW_____ NETNAME: ________ APPLID: ________ CATEGORY: ________ LIBQUE: ____________________________________________ 1(71) <=MORE=> S USERID ACTN VARIABLE DATA / ERROR MESSAGE - -------- ---- - 0...+...10....+...20....+...30....+...40....+...50....+...60. _ SJJ ERR BIMFTRDP-2 BIMXPCMD-2211 INPUT LINE LONGER THAN SEND-BUFFER, SJJ UPLD PMSCTRCS D _ SJA OK SJA DNLD NEWMAST PROC USED BY TURNOVER TO CREATE NEW MAST _ SJA OK SJA DNLD TURNOVER PROC CHKI SOURCE/REP LISTING/MOVE PHASE _ SJA OK SJA DNLD BIMFTR 21173 LD3 1 12/04/97 08:58:33 33 _ SJA OK SJA DNLD BIMFTR 21173 LD3 1 12/04/97 08:58:33 33 _ DDW OK DDW DNLD PR-GROUP 22035 LD3 1 STAT 12/09/97 12:55:47 100 _ DDW OK DDW DNLD BIMFTRTT PHASE 97-07-13 - - 512 B APHASE _ DDW OK PRESS PF8 TO SCROLL TO MORE EVENTS PF2=REF PF3=END PF8=FWD PF10=LEFT PF11=RIGHT PF12=DETAIL




This screen is used to display all of the transfer events currently contained in theActivity Log. The display begins with the most recent entry on the log. You canpress PF8 to scroll through the events from the newest event to the oldest event.To reposition the display to the most recent event, press PF2.

The fields at the top of the display, (USERID, NETNAME, APPLID, CATEGORY,and LIBQUE), are used to qualify the transfer events that will be displayed. Eachof the fields can be specified as a ‘generic mask’. Refer to the section “DownloadSelection Dialog” on page 97 for a description of generic.

The remainder of the screen contains one line for each transfer event on theActivity Log. The display is organized in date/time sequence, from new to old.

Each transfer contains two event entries. A “transfer begin” entry identified bythe ACTNs “UPLD” or “DNLD”, and a “transfer completion” entry identified bythe ACTNs “OK” or “ERR”.

The main body of the display contains many more fields that can be displayed oneven a model-5 3270. The “MORE” indicator on the right side of line 5 lets youknow which scroll keys you can press to see additional fields. The fields “S”,“USERID” and “ACTN” remain fixed on the screen. The remaining fields willscroll to reveal other fields describing each transfer event.

MORE=> indicates that PF11 can be pressed to see more fields to the right.

<=MORE indicates that PF10 can be pressed to see more fields to the left.

<=MORE=> indicates that more fields are available to the left and the right.

USERID

This field (on line 3) can be used to limit the display to transfer events for aspecified PC user id. This field can be specified as a generic mask to displayevents for related user ids.

NETNAME

This field (on line 3) can be used to limit the display to transfer events for aspecified VTAM netname. This field can be specified as a generic mask to displayevents for related netnames.

APPLID

This field (on line 3) can be used to limit the display to transfer events for aspecified VTAM applid. This field can be specified as a generic mask to displayevents for related applids.

CATEGORY

This field (on line 4) can be used to limit the display to transfer events for aspecified transfer category. This field can be specified as a generic mask todisplay events for related categories.



LIBQUE

This field (on line 4) can be used to limit the display to transfer events for aspecified transfer LIBQUE. This field can be specified as a generic mask todisplay events for related LIBQUEs. Refer to the section “Category DefinitionScreen” on page 195 for a description of the various LIBQUE values that can bespecified.

nnn(mmm)

This field displays the current position in the Activity Log. ‘nnn’ is the currentevent number. The most recent event has a number 1. ‘mmm’ is the total numberof events contained in the Activity Log.

S

This field is active on all transfer completion events. To see the detail for an eventon the “Transfer Event Display”, enter any non-blank value in this field andpress ENTER.

USERID

This field (starting on line 8) displays the PC user id for each transfer event.

ACTN

This field displays the type of each transfer event:

UPLD start of an upload from a PC to the hostDNLD start of a download from the host to a PCOK successful completion of a transferERR error completion of a transfer

NETNAME

This field (starting on line 8) displays the VTAM netname of the PC used for eachtransfer event.

MM/DD

This field displays the month and day on which each transfer event occurred.

HH:MM:SS

This field displays the time at which each transfer event occurred.

CATEGORY

This field (starting on line 8) displays the transfer category for each transferevent.



LINE CNT

This field displays the number of host data lines/records that were transferred.This count does not include any CRLF lines inserted by the PC to account forreport line spacing in POWER or JES.

BYTE CNT

This field displays the number of bytes that were transferred. This count does notinclude any PC related overhead such as CRLFs.

DURATION

This field displays the length of time (hh:mm:ss) that it took to complete thetransfer.

CHR/SEC

This field displays the effective speed of the transfer as the number of bytes persecond. The higher the number, the faster the transfer.

LIBQUE

This field (starting on line 8) displays the transfer LIBQUE for each transferevent. Refer to the section “Category Definition Screen” on page 195 for adescription of the various LIBQUE formats that can be displayed.

LRECL

This field displays any LRECL that was specified by the PC to be used for thetransfer. If this field is blank, no LRECL was specified.

TC

This field displays The ‘ASCII Translate’ and ‘CR/LF’ options that were specifiedon the PC. If ‘*’ is displayed, then the PC specified that the ‘default’ action shouldoccur.

R

This field displays The ‘Duplicate Files’ option that was specified on the PC. If ‘*’is displayed, then the PC specified that the ‘default’ action should occur. Othervalues can be:

R replaceN create newA append to existing file

PC PATH

This field displays the location of where the transferred file originated on the PCfor uploads, or where the file was sent on the PC for downloads.



APPLID

This field (starting on line 8) displays the VTAM applid of the host CICS or BIM-TMAN system that was being used for the transfer.

TFR-TYPE

This field displays the method that was used to initiate the transfer:

MANUAL Transfer performed using the main PC transfer program.AFT Transfer performed using the Automatic Transfer Program

initiated from the PC.HOSTAFT Transfer performed using the Host Initiated Automatic

Transfer Feature.

CONNECTION

This field displays the type of connection between the PC and the Host:

APPC APPC connection.LU2 LU2/3270 connectionIP=xxx.xxx.xxx.xxx TCP/IP connection

HOSTAFT SCRIPT

This field displays the name of the HOSTAFT script that was used for thistransfer. This field will be blank unless TFR-TYPE is HOSTAFT.

JOBNAME

This field displays the job name of the job that activated the HOSTAFT script thatwas used for this transfer. This field will be blank unless TFR-TYPE is HOSTAFT.

VARIABLE DATA / ERROR MESSAGE

This field displays for transfer begin events, the data fields that describe theactual entity that is being uploaded or downloaded. The data in this field isdependent on which CATEGORY is being used, and whether it is an upload or adownload. The data matches the fields documented for each CATEGORY driverfor its upload and download dialogs. Refer to the section “Driver Specifications”on page 306 for additional information.

For transfer error completion events, this field contains the text of the messagethat describes the reason that the transfer could not complete.



Transfer Event Display

This screen can be displayed by either pressing PF12 or entering a non-blank inan “S” field for a specific transfer completion event, and pressing ENTER. Ascreen similar to the following will be displayed:

*** BIM-PC/TRANSFER *** TRANSFER EVENT DISPLAY yyyy/mm/dd hh:mm:ss

EVENT TYPE: UPLD START: 04/11 09:17:18 LINES: COMPLETION: ERR END: 04/11 09:17:20 BYTES: 39(71) DURATION: 00:00:02 CHAR/SEC: APPLID: BIMCICST TFR-TYPE: HOSTAFT USERID: DDW SCRIPT: HOST SCRIPT ONE NETNAME: LI2D JOBNAME: TESTJOB1 CATEGORY: EDIT LIBQUE: DDW PC PATH: C:\DATA\BMAIL.TXT LRECL: CRLF: * TRANSLATE: * RNA: N MORE=> VARIABLE DATA / ERROR MESSAGE 0...+...10....+...20....+...30....+...40....+...50....+...60....+.. DATA: BMAIL TEXT MESSAGE: BIMFTRDE-2 (BIGDPTXM) ** MEMBER "DDW.BMAIL" ALREADY EXISTS **

PF2=REF PF3=END PF4=RETN PF7=BWD PF8=FWD PF10=LEFT PF11=RIGHT

This display combines the transfer completion event, and its correspondingtransfer begin event into a single screen.

The fields displayed are the same as the fields described for the “TransferActivity Log Display” above.

You can press PF7 and PF8 to scroll from one event to the next. When you exitthis display using PF4, the event currently being displayed will become the firstevent displayed on the Transfer Activity Log Display.

The selection fields: USERID, NETNAME, APPLID, CATEGORY and LIBQUE onthe “Transfer Activity Log Display” will control which events are displayed onthis screen.


Page 260 Printing The Host Transfer Activity Log

Printing The Host Transfer Activity LogBIM-PC/TRANSFER can optionally maintain an Activity Log of all transfers thatare performed. This Activity Log is maintained by the host software in a VSAMRRDS dataset that was defined and initialized during the installation of thisproduct.

This section describes the options available for printing all or portions of the HostActivity Log. Refer to the section “Viewing The Host Transfer Activity Log(FTRL)” starting on page 251 for information on viewing the Host Activity Log.

The Activity Log processing is activated by setting the option “GENERATEEVENT LOG” to “Y” on the “System Options Screen” which begins on page 191.

The Activity Log is a ‘wrap-around’ file. That means that you define the file tohold a specific number of events. Once that number of events has been logged,the file wraps. From that point on, the Activity Log will contain the most recent‘nnnnn’ transfer events, where ‘nnnnn’ is the number of events that the file wasdefined to hold. Each transfer requires two events, one for the transfer begin, andthe other for the completion.


Printing The Host Transfer Activity Log Page 261

Sample Report

The format of the Transfer Activity Report is similar to the “Transfer EventDisplay”. Refer to the section “Viewing The Host Transfer Activity Log (FTRL)”starting on page 251 for information on each field in the report.

SYSIN: PRINT LOGFILE NEWEVENTS INCLUDE(USERID(DDW,SJA))

BIMFTRPR-2 NEWEVENTS PROCESSING WILL RESUME FOLLOWING THE EVENT THAT OCCURRED ON 1997/01/27 AT 13:04:39BIM-PC/TRANSFER ---- TRANSFER ACTIVITY LOG PRINT UTILITY ---- 08.49 PAGE 1REL. x.xx 01-31-1997 (1997/031)

EVENT TYPE: DOWNLOAD START: 1997/01/27 07:58:06 LINES: 13 APPLID: BIMCICSTCOMPLETION: OK END: 1997/01/27 07:58:15 BYTES: 684 CATEGORY: EDIT USERID: SJA DURATION: 00:00:09 CHAR/SEC: 76 LIBQUE: BIMFTR NETNAME: MYPC CONN: IP=172.17.2.1 TRANSLATE: * CRLF: * RNA: LRECL: 0 TFR-TYPE: MANUAL SCRIPT: JOBNAME: PC PATH: C:\DATA\PLANETS.DAT VAR. DATA: PLANETS

EVENT TYPE: DOWNLOAD START: 1997/01/27 07:58:49 LINES: 13 APPLID: BIMCICSTCOMPLETION: OK END: 1997/01/27 07:58:55 BYTES: 684 CATEGORY: EDIT USERID: SJA DURATION: 00:00:06 CHAR/SEC: 114 LIBQUE: BIMFTR NETNAME: Q008 CONN: LU2 TRANSLATE: * CRLF: * RNA: LRECL: 0 TFR-TYPE: HOSTAFT SCRIPT: HOST SCRIPT ONE JOBNAME: HOSTJOB1 PC PATH: C:\DATA\PLANETS.DAT VAR. DATA: PLANETS

EVENT TYPE: DOWNLOAD START: 1997/01/31 08:46:28 LINES: 191 APPLID: BIMCICSTCOMPLETION: OK END: 1997/01/31 08:46:33 BYTES: 15,005 CATEGORY: POWER USERID: DDW DURATION: 00:00:05 CHAR/SEC: 3,001 LIBQUE: LST NETNAME: TR41 CONN: APPC TRANSLATE: N CRLF: * RNA: LRECL: 0 TFR-TYPE: AFT SCRIPT: JOBNAME: PC PATH: C:\BIMFTR\BIMLNKQS.LST VAR. DATA: BIMLNKQS 92 LL3 1 12/23/95 00.35.38 191 6 DAVE R000

BIMFTRPR-1 LOG FILE PRINT COMPLETE, 3 EVENTS READ, 3 EVENTS PRINTED

Program BIMFTRPR

The program BIMFTRPR is used to print the contents of the Host Activity Log.The following JCL is required to execute program BIMFTRPR:

VSE JCL to Execute BIMFTRPR

// JOB FTRPRINT// DLBL BIMFTRL,'BIMPCTFR.LOG.FILE',,VSAM// LIBDEF PHASE,SEARCH=lib.sublib// EXEC BIMFTRPR,SIZE=AUTOPRINT LOGFILE .../*/&



MVS JCL to Execute BIMFTRPR

//jobname JOB//STEP1 EXEC PGM=BIMFTRPR//STEPLIB DD DSN=bimpctfr.loadlib,DISP=SHR//BIMFTRL DD DSN=BIMPCTFR.LOG.FILE,DISP=SHR//SYSPRINT DD SYSOUT=*//SYSIN DD *PRINT LOGFILE .../*//

Commands and Operands for BIMFTRPR

Parameter cards must be supplied to program BIMFTRPR to specify whichActivity Log events are to be printed.

Syntax

The syntax of BIMFTRPR's Commands is the same as the one used by the IBMutility IDCAMS:

• A Command followed by keyword Operands, with the value to be assignedto a keyword specified in parentheses.

• Blanks or commas are used to separate Operands from the Command andfrom other Operands.

• Continuation is specified by coding a dash as the last non-blank on the lineto be continued.

• Comments may appear before, between, and/or after Operands.

• A comment starts with the characters "/*", is ended by the characters "*/",and may be continued to multiple lines as needed.

In the following instructions, the BIMFTRPR Commands and Operands shouldbe interpreted as follows:

• UPPER CASE = the exact characters to be entered

• lower case = values to be supplied by you

• boldface/underlined keywords or values = default values

• Vertical bar "|" separates mutually exclusive Operands

• [values enclosed in brackets] are optional

Refer to “APPENDIX A” starting on page 459 for a more complete description ofhow to code Commands and Operands.



PRINT Command

The PRINT Command is used to specify which Activity Log events are to beprinted.

Any number of PRINT Commands can be specified in a single execution ofprogram BIMFTRPR.

How to enter

PRINT LOGFILE - [ALLEVENTS|NEWEVENTS|NEWEVENTSFINAL -] [EXCLUDE(field list...) -] [INCLUDE(field list...)]

Explanation

LOGFILE

This operand specifies that this PRINT command refersto the Activity Log File. Future releases of BIM-PC/TRANSFER may support additional PRINTfunctions.

ALLEVENTS|NEWEVENTS|NEWEVENTSFINAL

This operand specifies which log records are to beconsidered for printing:

ALLEVENTS All events are to be considered.

NEWEVENTS Only events that have occurredsince the last use of theNEWEVENTSFINAL operand are tobe printed.

NEWEVENTSFINALOnly events that have occurredsince the last use of theNEWEVENTSFINAL operand are tobe printed. After printing iscompleted, the location of the lastprinted event is recorded in the logfile.

The NEWEVENTSFINAL operand requires update accessto the log file.



EXCLUDE(field list...)INCLUDE(field list...)

These operands can be used to specify selection criteriafor which events are to be printed. Any number of theseoperands can be specified, in any sequence. They will beprocessed in the order they are specified.

If only EXCLUDE operands are specified, then alltransfer events are printed unless specifically excluded.If one or more INCLUDE operands are specified, thenNO transfer events will be printed unless specificallyincluded.

Field List Operands

The syntax of the EXCLUDE and INCLUDE operands is as follows:

EXCLUDE( field1(list1) [field2(list2)...]) ...

INCLUDE( field1(list1) [field2(list2)...]) ...

The 'fieldn(listn)' Operands represent the names of the fields to test and the datato be tested for.

• Any number of 'fieldn(listn)' Operands can be specified.

• If more than one 'field(list)' Operand is specified, ALL fields must be'matched' for the transfer event to be printed.



Field name Keywords

Each of these keywords represents a field printed on the report. Refer to thesection “Viewing The Host Transfer Activity Log (FTRL)” starting on page 251for information on each of these fields.

APPLID(string …) (1 - 8 characters)BYTES(number …) Number of bytes transferred. (1 - 9 digits)CATEGORY(string …) (1 - 8 characters)CHARSEC(number …) Characters per second (1 - 9 digits)COMPLETION(OK|ERROR)CONNECTION(string …) Type of connection between the PC and the

Host. Values are: APPC, LU2 orIP=xxx.xxx.xxx.xxx.

CRLF(string …) (1 character)DURATION(time …) Duration of transferENDDATE(date …) Date transfer endedENDDATETIME(date, time) Compares the date and time that the

transfer ended against the specified values.The time is only compared if the date isequal. Only a single date and time can bespecified for this Keyword.

ENDTIME(time …) Time transfer endedEVENTTYPE(UPLOAD|DOWNLOAD)HOSTAFTSCRIPT(string …) (1 - 16 characters)HOSTAFTJOB(string …) (1 - 8 characters)LIBQUE(string …) (1 - 44 characters) Refer to page 196 for a

table of valid libque values.LINES(number …) Number of lines transferred. (1 - 9 digits)LRECL(number …) LRECL specified for transfer. (1 - 9 digits)MESSAGE(string …) (1 - 72 characters)NETNAME(string …) (1 - 8 characters)PCPATH(string …) (1 - 72 characters)RNA(string …) (1 character)STARTDATE(date …) Date transfer startedSTARTDATETIME(date, time) Compares the date and time that the

transfer started against the specifiedvalues. The time is only compared if thedate is equal. Only a single date and timecan be specified for this Keyword.

STARTTIME(time …) Time transfer startedTRANSFERTYPE(MANUAL|AFT|HOSTAFT)TRANSLATE(string …) (1 character)USERID(string …) (1 - 8 characters)VARDATA(string …) (1 - 72 characters)



Field name Relational Operators

Field name keywords can be prefixed by a 'relational operator' to change themeaning of a 'match' with the strings or numbers in the specified list.

EQ field(...) (default) match if field is equal to any one value in listNOT field(...) match if the field is equal to NONE of the values in listNE field(...) match if the field is not equal to the string or numberGT field(...) match if the field is greater than the string or numberGE field(...) match if the field is greater than or equal to the string or

numberLT field(...) match if the field is less than the string or numberLE field(...) match if the field is less than or equal to the string or

number

(list) formats and rules• 'lists' can contain any number of data values to be tested against the 'field'. If

more than one value is specified, 'matching' any ONE value 'matches' the list.

• Data values can be ‘dates’, ‘times’, 'numbers' or 'strings' depending on the'field' being used. Refer to the “Field name Keywords” list above.

• Any or all data values within a 'field' list can be qualified by specifyingadditional selection criteria:

field1( value1 (INCLUDE ( field (list) …) …) value2 …)

If 'value1' matches the test for 'field1' then the selection criteria specifiedfollowing value 1 will be tested, and if that selection criteria 'matches', thenthe 'field1' list is 'matched'. If the selection criteria for 'value1' does NOTmatch, then 'value1' is considered NOT a match and 'value2' will be tested.

Selection criteria can be nested up to a limit of 30 '(' from the start of theCommand.

Rules for numbers as values• 'numbers' cannot contain commas or periods, but can be preceded by a '+' or

'-'. (See special rules for date and time values.)

• 'numbers' must be specified in the exact format defined for the 'field' beingused. Refer to the “Field name Keywords” list above.

Rules for Date and Time values• Dates can be specified as:

yy/ddd (must be entered as 6 characters, 96/001)yyyy/ddd (must be entered as 8 characters, 1996/001)yy/mm/dd (must be entered as 8 characters, 96/01/01)yyyy/mm/dd (must be entered as 10 characters, 1996/01/01)



+n-n

If the value is preceded by either a '+' or '-' it is assumed to be an adjustmentfrom the 'current' system date. Example - if today is 96/01/11 andSTARTDATE(-10) is entered, then DATE(96/01/01) is used. IfSTARTDATE(-1/000) is entered, then DATE(95/01/11) is used.

If the year is entered as 'yy', the current century is assumed.

• Times can be specified as either:

hh:mmhh:mm:ss

Times are assumed to be 24 hour (military) time.

Rules for strings as values• 'strings' can be any character string. If it contains any blanks, commas, quotes

or parenthesis, enclose the string in single quotes. If the string contains anyquotes, specify them as (2) single quotes.

• 'strings' can contain special 'generic' operators.

'*' represents ANY number of characters.'+' represents ANY single character.

If you need to specify a string with an '*' or '+' and you want to test for thosecharacters, specify the string as - C'string'.

• 'strings' can be specified as hexadecimal values - X'hhhhhhhh'.

• 'strings' can be specified such that they represent a portion of the keyword'field' by specifying them in the following format:

'string'/offset/length

where 'offset' is the number of bytes from the start of the 'field', relative tozero, and 'length' is the number of bytes to be tested. If only 'offset' isspecified, the length of the 'string' is used for 'length'.



Sample Print Commands

Assume you want to print all transfers that meet the following criteria:

• The transfers were performed using the CICS with applid ‘BIMCICST’.

• The transfers were performed by users ‘SJA’ or ‘DDW’.

• You want to see only the ‘uploads’ done by ‘SJA’ and the ‘downloads’ doneby ‘DDW’.

• You are only interested in activity performed between 95/08/01 at 13:00 and95/08/02 at 08:00. Dates for the current century can be entered with either 2or 4 digit years as shown in the following examples.

Each of the following commands will perform this search:

PRINT LOGFILE - EXCLUDE(NE-APPLID(BIMCICST)) - EXCLUDE(LT-STARTDATETIME(1995/08/01,13:00:00)) - EXCLUDE(GT-STARTDATETIME(1995/08/02,08:00:00)) - INCLUDE( - USERID(SJA) - EVENTTYPE(UPLOAD) - ) - INCLUDE( - USERID(DDW) - EVENTTYPE(DOWNLOAD) - )

PRINT LOGFILE - EXCLUDE(NE-APPLID(BIMCICST)) - INCLUDE( - GE-STARTDATETIME(95/08/01,13:00:00) - LE-STARTDATETIME(95/08/02,08:00:00) - USERID( - SJA(INCLUDE(EVENTTYPE(UPLOAD))) - DDW(INCLUDE(EVENTTYPE(DOWNLOAD))) - ) - )



PRINT LOGFILE - INCLUDE( - APPLID(BIMCICST) - GE-STARTDATETIME(95/08/01,13:00:00) - LE-STARTDATETIME(95/08/02,08:00:00) - EVENTTYPE( - UPLOAD(INCLUDE(USERID(SJA))) - DOWNLOAD(INCLUDE(USERID(DDW))) - ) - )

PRINT LOGFILE - EXCLUDE(NE-APPLID(BIMCICST)) - EXCLUDE(LT-STARTDATETIME(95/08/01,13:00:00)) - EXCLUDE(GT-STARTDATETIME(95/08/02,08:00:00)) - INCLUDE( - USERID( - SJA(INCLUDE(EVENTTYPE(UPLOAD))) - DDW(INCLUDE(EVENTTYPE(DOWNLOAD))) - ) - )

Sample Two

Assume you want to print all transfers that ended in an error with messagesBIMFTRDV-12 or BIMFTRDV-13:

PRINT LOGFILE - INCLUDE( - COMPLETION(ERROR) - MESSAGE( *BIMFTRDV-12* *BIMFTRDV-13* ) - )

In the above example we specified an ‘*’ before and after the message numbers sothat they will be found anywhere in the message text.


Page 270 BIMFCV - File Conversion Program

BIMFCV - File Conversion UtilityBIMFCV is a MS-DOS program that can be used to convert a mainframe file thathas been downloaded to the PC into a format acceptable for input into most PCsoftware products.

This program can be run in native DOS, or from a DOS window in MicrosoftWindows or OS/2.

The mainframe file must have been downloaded without translation, andwithout CRLF insertion.

The OUTPUT operand of the #OPTION statement is used to specify the format ofthe converted file.

BIMFCV takes input logical records and selectively converts individual datafields into an output ASCII file. Data conversion rules and output file formats arecontained in a File Conversion Script (refer to the section “File ConversionScripts” on page 271). Generally, there will be a one-to-one relationship betweeninput logical records and lines in the resulting output ASCII file.

BIMFCV runs from the DOS command line and takes three command linearguments:

BIMFCV input.file output.file script.file

input.file This is the full path name for the input file to be converted.

output.file This is the full path name for the output file that will becreated by BIMFCV.

script.file This is the full path name for the File Conversion Script thatis to be used to convert the input file.

If you omit one or more of these file names, you will be prompted for the filenames.

Customizing BIMFCV

You can use the #OPTION statement of the File Conversion Script to makechanges to BIMFCV's operation. If desired, you can optionally make the changesglobal. Using any ASCII text editor, edit file BIMFCV.INI. You will find the samefour options as described for the #OPTION statement. Changing their valuesthere will affect all executions of BIMFCV.


File Conversion Scripts Page 271

File Conversion ScriptsA File Conversion Script is a sequence of field definitions and control statementswhich operate together as instructions for conversion of host files into ASCIIoutput files.

File Conversion Scripts can either be used by the File Conversion Utility(BIMFCV) on the PC, or they can be used by the Host during downloads.

Scripts used on the Host for downloads can be created on the PC and uploadedusing a Category defined for driver BIMFTRDX, or they can be defined directlyon the Host using the FTRM transaction.

Host Scripts can be specified by the PC user for any download using the“Download Script Name” field of the Download Selection Dialog.

The File Conversion Script consists of 16 different kinds of statements:

Command Description Page* Comment 272#OPTION Processing Options 273name ... Field Definition 275#RECORD Record description 279#PROMPT User Prompt for processing options 280@name Label 282#IF If 283#GOTO Go to 285#ERROR Error Message 286#GROUPBEG Group begin 287#GROUPEND Group End 287#CRLF Carriage-return/Line-feed 290#INSERT Insert literal 291#LINE Insert Line 292#SKIP Skip Record 294#END End of record 293

Each of these is described below.


Page 272 File Conversion Scripts

Notes on Syntax:• Words in UPPER CASE must be keyed in upper case.

• Words in lower case indicate places where you may be creative in assigningnames to things, or where several options exist for the entry.

• Individual operands within statements are separated by spaces.

• Scripts that will be used by the Host for downloads have the followingrestrictions:

1) Each line of the script must be no longer than 72 characters.

2) Script definitions are limited to 400 lines.

The examples and descriptions below assume the presence of a COBOL filedefinition for the mainframe file (although that is not necessary).

Comments

* whatever commentary needed

Comments begin in column one with an asterisk ('*'). A comment line is ignoredwhen processing the File Conversion Script.



Processing Options

Processing options can be imbedded in the script. There are four different optionsthat can be specified. The defaults in effect are highlighted in the modelstatement below. You only need to supply an #OPTION statement if you need tochange one or more of the settings.

#OPTION ASCII=YES|NO EOF=YES|NO SEPARATOR=, DECIMALPT=.

#OPTION OUTPUT=ASCII|NOSEP|.WK1|.WKS|.WKQ|.WQ1|.WRK|.WR1

#OPTION OUTPUT=ASCII,APPEND (program BIMFCV only)

ASCII=YES|NO

ASCII files need to be treated differently than othertypes of input files (refer to the section “ProcessingASCII Files” on page 301 for more information).

EOF=YES|NO

Some PC programs require an end-of-file marker in theoutput. The end-of-file marker is an “F6” or X'1A'. Thisis particularly true of older PC software. Consult thedocumentation for the program(s) that will beprocessing the converted output file. If you need theend-of-file marker, specify EOF=YES.

SEPARATOR=,

Most PC software will accept a comma (',') as theseparator between fields for their input files. If not, youcan specify a different character here. (You will need tochange this if your character fields will themselvescontain imbedded commas. You may also need tochange it depending on the setting for DECIMALPTbelow.)

DECIMALPT=.

International users will probably have to change thissetting. The DECIMALPT is used when convertingnumeric data using the “9.” conversion option (seebelow).

OUTPUT=ASCII|NOSEP|.WK1|.WKS|.WKQ|.WQ1|.WRK|.WR1OUTPUT=ASCII,APPEND (program BIMFCV only)

This option defines the format of the output file. Thedefault is a standard separator delimited ASCII file. Theother supported formats are:



NOSEP An ASCII file without the separators betweenfields

.WKS Lotus 1-2-3 release 1 and 1A

.WK1 Lotus 1-2-3 release 2.x

.WKQ Borland Quattro

.WQ1 Borland Quattro Pro

.WRK Symphony release 1.0

.WR1 Symphony releases 1.1, 1.2 and 2.x

APPEND can only be specified in scripts being executedby program BIMFCV. This option causes an existing PCfile to be extended.



Field Definitions

name type offset length convert repeat OLEN=n

The Field Definition defines an individual field in the record. There must be atleast one field definition for every field you want to appear in the converted file.

There are six parts to the field definition:

name

A name is always required. The name need not be unique withinthe File Conversion Script unless it is referenced in an #IF or#GROUPBEG directive. To avoid conflict with other directives inthe File Definition Script, the name cannot begin with an asterisk'*', a pound-sign '#', a number (0-9), or an at-sign '@'. All othercharacters on the PC keyboard are available for your use. Thename can be up to 30 characters long but may not includeimbedded spaces.

type

The type describes the format of the field on the input file. It canbe one of:

X Character data (e.g. PIC X(4) )C Character dataZn Zoned decimal (e.g. PIC 999 )Bn Binary (e.g. PIC S9(4) COMP )Pn Packed decimal (e.g. PIC S9 COMP-3 )

Types “X” and “Z” fields will have leading and trailing blanksremoved prior to being converted for output. Type “C” fieldswill not have blanks removed.

The numeric types (Z, B, P) can optionally be followed by anumber that indicates the number of decimal places in the field.(For example, a COBOL PIC S9(4)V99 might have a type of P2for two decimal places.) This optional number of decimal placesplus the convert option below will determine how the number isformatted in the output file.

offset

This is the offset of the field within an individual file record,relative to zero. That is, the first byte of the record is offset 0, thesecond, offset 1, etc. The offset is required for all field definitions.

The offset may also be an asterisk ('*'). An asterisk specifies thatthe current position in the input file be used for the offset.



Understand that using an asterisk implies that every fieldpreceding this one is present in the File Definition Script - this isnot always otherwise necessary.

length

This is the actual length of the field in bytes. This is easy for aCOBOL PIC X(nn) field, and somewhat tricky for packed andbinary fields. Some examples are shown below:

COBOL PIC LengthPIC S9(4) COMP 2PIC X(10) 10PIC 9(5) 5PIC S9(7)V99 COMP-3 5

convert

This determines how the field will be formatted in the outputfile. Convert must be one of the following:A Convert to ASCIIA' Convert to ASCII, delimit with 'sA" Convert to ASCII, delimit with "sN No conversion, just moveN' No conversion, delimit with 'sN" No conversion, delimit with "s9 Convert to character numerics9. Convert to character numerics adding a decimal point as

neededO Do not move to output file (this is a character O not a zero).

This option may be necessary in some situations - see the#IF statement below.

E De-edit a COBOL edited PIC. (Another way of looking atthis is to extract numbers only. For instance, the COBOLPIC $$$$9.99 might result in $$145.66, this convert willextract 145.66. This is used with ASCII files (see below).

The three different ASCII conversion options treat character datain slightly different ways. For example, suppose we have a 19character field that contains: BIMFTR IS WONDERFUL. Theresulting conversion will be:

A BIMFTR IS WONDERFULA' 'BIMFTR IS WONDERFUL'A" "BIMFTR IS WONDERFUL"

Likewise, in combination with the type described above, the twonumeric conversion options create different results. This time,suppose we have a numeric field defined of length 4. Theresulting conversion will be:



field type convert result1234 Z 9 12341234 Z2 9 12341234 Z2 9. 12.340022 Z2 9 220022 Z1 9. 2.20022 Z2 9. 0.220000 Z2 9. 0

repeat

Optional entry which specifies the number of times the fieldoccurs at this offset. For example, a field with COBOL PIC X(4)OCCURS 4 TIMES would have a repeat value of 4.

OLEN=n

Optional entry which specifies the length of the data in the PCfile. The output length is normally determined dynamically by acombination of the 'type' and 'convert' fields. This field can bespecified to override that calculation. 'n' specifies the desiredlength. Character fields will be left justified and space filled.Numeric fields will be right justified and zero filled. If the inputdata is longer than the OLEN value, it will be truncated.

Example:

Consider the following COBOL record definition.

01 RECORD-ONE. 05 TRANSACTION PIC X. 05 TRAN-DATE PIC X(8). 05 TRAN-TIME PIC X(8). 05 TRAN-NUMBER PIC 9(8). 05 TRAN-WHOM PIC X(8). 05 TRAN-AMT PIC S9(7)V99 COMP-3. 05 TRAN_CODES PIC XX OCCURS 4.

The field definitions would look like:

TRANSACTION X 0 1 ATRAN-DATE X 1 8 ATRAN-TIME X 9 8 ATRAN-NUMBER Z 17 8 9TRAN-WHOM X 25 8 A'TRAN-AMT P2 33 5 9.TRAN_CODES X 38 2 A 4

And a converted record might look like:

U,08/03/93,14:44:22,12300678,'BIG DOG ',37.45,A1,,,,



Note, only one TRAN-CODES entry (A1) appears in the sample converted recordabove. The conversion process eliminated fields containing all spaces (or binaryzeroes), but the associated commas were preserved. Trailing spaces are notremoved from a delimited string.

Note also, since TRAN-NUMBER is of type Z (zoned decimal), its convert couldalso have been A for ASCII without any change in the resulting output. Unlessyou need decimal point conversion, a type Z convert 9 is interchangeable with atype X convert A.



Record Descriptions

#RECORD type minimum maximum

The RECORD statement defines the type and length of a logical record within afile. You must include at least one of them in the File Definition Script.

type

This is the record type and is either:

F Fixed length, orV Variable length.

The only record that qualifies for the specification of V is onethat contains a COBOL OCCURS DEPENDING ON clause in itsdefinition or otherwise operates identically. All other recordsshould be specified as F for fixed length, even though you mayhave records of different length within the file. (A file containinga variable record that does not rely on the COBOL OCCURSDEPENDING ON construct is beyond the scope of this scriptinglanguage.)

If you are working with a file that contains several differentrecord types, each of varying length, then you will need tosupply a #RECORD statement for each of the various recordtypes in the file. The #IF statement (below) is then used todetermine which #RECORD statement applies.

minimum

This is the minimum or only length for the record.

maximum

This is the maximum length for a variable length record. It isneither needed nor used for fixed length records.

Examples:

#RECORD F 124

Record is fixed length, 124 bytes long.

#RECORD V 100 300

Record is variable in length and ranges from 100 to 300 bytes inlength.



#PROMPT

The #PROMPT statement can be used to request input from the PC user prior tostarting a file conversion.

#PROMPT %fldname DEFAULT=default - TYPE=X|N - RANGE=(from,to) - LIST=(xxx,yyy,zzz,...) - HDG='heading text' - LENGTH=n

You can specify as many #PROMPT statements as required for your script. Theymust all appear at the beginning of your script.

The #PROMPT statement can be continued to multiple script lines by specifyinga '-' as the last character of each line except the last line of the statement.

%fldname

Required. This is the field identifier that can appear in asubsequent #IF statement. 'fldname' can be any characters, up to8 in length. The '%' is required as the first character.

LENGTH=n


DEFAULT=default


Note: If a LIST operand is provided, and the DEFAULT operandis omitted, the 1st value in the LIST is used for the default.

TYPE=X|N

Specifies the type of field. 'X' for character, 'N' for numeric. Thedefault is 'X'.

RANGE=(from,to)

Optional operand that provides range edits for data entered bythe PC user. If the field type is character, and the entered datacan contain spaces, the from and to values must be specifiedwithin quotes. This operand is mutually exclusive with the LISToperand.




Optional operand that provides a list of valid responses that canbe entered by the PC user. If the field type is character, and theentered data can contain spaces, the individual values in the listmust be specified within quotes. This operand is mutuallyexclusive with the RANGE operand.

HDG='heading text'


Example:

#PROMPT %FLD1 HDG='Select Record Type' - LENGTH=7 - LIST=(MASTER,ACCT,LICENSE)

In this example, prompt field %FLD1 is defined as a 7 character field. The PCuser can respond with one of three choices: MASTER, ACCT or LICENSE. Theimplied default is MASTER.



Labels

The #IF statement (below) may cause processing to skip around within the FileConversion Script. The Label statement defines the location for processing tocontinue whenever a #IF statement is evaluated as true.

@name

name


Example:

@HAPPYHOUR



#IF

The #IF statement allows you to jump around within the File Conversion Script.Its primary and most common use will be to properly handle different recordtypes within the file.


field

Is the name given on a previously defined field definition or a%fldname from a #PROMPT statement.

condition



comparand

This is either a literal or a %fldname from a #PROMPTstatement. It will be compared to the field above. Literals thatcontain embedded spaces must be enclosed within single quotes.Numbers cannot contain commas or periods. Literals may alsocontain hexadecimal characters - see “Character Strings” belowfor more information.

label

This is the label name where processing will resume if thecomparison specified in the #IF statement evaluates to true. Ifthe comparison evaluates to false, the next sequential statementin the File Conversion Script will be processed.


Example:

BEAN-TYPE X 7 1 O#IF BEAN-TYPE = G GARBONZOS • • •@GARBONZOS • • •



Here the field “BEAN-TYPE” is given a conversion of “O” foromit. This was done to keep the field out of the output file, yetmake it available for use in the #IF statement following. The #IFchecks the field “BEAN-TYPE” for the literal “G”. If a “G” isfound, processing will proceed to the statements following thelabel “GARBONZOS.” If a “G” is not found, other processing(not shown) will take place.



#GOTO


#GOTO label

label





#ERROR

It is useful during testing of a File Conversion Script to insert error messages hereand there within the script. The #ERROR statement allows for this.

When a #ERROR statement is encountered, the associated message is displayedon the PC screen and script processing for the file is terminated.

#ERROR message

message

Any meaningful message that will aid in diagnosis of a problemin the script.

Example:

BEAN-TYPE X 7 1 O#IF BEAN-TYPE = G GARBONZOS#IF BEAN-TYPE = L LIMAS#ERROR Invalid BEAN-TYPE encountered • • •@GARBONZOS • • •

This is a continuation of the example above. Here, we are alsochecking for a “BEAN-TYPE” of “L.” If the “BEAN-TYPE” isneither “G” or “L”, the error message “Invalid BEAN-TYPEencountered” will be displayed on the PC screen and processingwill be terminated.



#GROUPBEG - Group Begin#GROUPEND - Group End

The Group Begin statement is used to inform the script processor about tableentries within an input file. The table is delimited by #GROUPBEG and#GROUPEND statements.

#GROUPBEG offset occurs SEPARATE

offset

Like field definitions described above, this is the offset within thefile where the group begins. It can also be an asterisk ('*') torequest dynamic offset calculation. The asterisk option isprimarily used for defining COBOL OCCURS DEPENDING ONwithin an OCCURS DEPENDING ON type of data construct.

occurs

The occurs value can be either a number for a table with a fixedcount of entries, or a previously defined field name for a tablewith a variable number of entries.

SEPARATE

This parameter is optional. If present, each occurrence of thegroup will be written to the output file as a separate record. (Seeexample 3 below for more information.)

#GROUPEND

There are no operands on a #GROUPEND statement. It merely marks the end ofthe table or group within the input file. There must be a corresponding#GROUPEND for every #GROUPBEG within the File Conversion Script.

Special Considerations

Group processing introduces some special considerations when creating a FileConversion Script:

1) Offsets of fields defined with a group begin at 0 for the first field in thegroup. Offsets for field definitions following a table entry should revert to therecord or previous group sequence (see example below).

2) Every field found within a table entry in the input file must have acorresponding field definition within a group. If you do not want the field(s)to be converted into the output file, you can use the conversion of “O” foromitted. This is required because the script processor dynamicallydetermines the length of each group as it works its way through the FileConversion Script.



Refer to the section “Files Containing a COBOL OCCURS DEPENDING ONclause” starting on page 298 for more information about groups and how toproperly use them.

Examples:1) Suppose your input file contains the following table:

05 TABLE-1 OCCURS 5 TIMES. 10 ITEM-1 PIC X(4). 10 ITEM-2 PIC S9(5) COMP-3. 10 ITEM-3 PIC S9(7)V99 COMP-3.05 BIG-NAME PIC X(30).

Its field definitions would then be:

#GROUPBEG * 5ITEM-1 X 0 4 AITEM-2 P 4 3 9ITEM-3 P2 7 5 9.#GROUPENDBIG_NAME 400 X 30 A"

2) Suppose instead that the table looked like this:

05 TABLE-CNT PIC S9(4) COMP.05 TABLE-1 OCCURS 0 TO 10 TIMES DEPENDING ON TABLE-CNT. 10 ITEM-1 PIC X(4). 10 ITEM-2 PIC S9(5) COMP-3. 10 ITEM-3 PIC S9(7)V99 COMP-3.05 BIG-NAME PIC X(30).

Its field definitions would then be:

TABLE-CNT B 338 2 9#GROUPBEG 340 TABLE-CNTITEM-1 X 0 4 AITEM-2 P 4 3 9ITEM-3 P2 7 5 9.#GROUPENDBIG_NAME X * 30 A

NOTE: In the example 2 above, the field “BIG-NAME” uses the asterisk asoffset. You must use the asterisk in this case since you cannot predict whatthe offset will be without examining the individual record.

3) You may need to create separate records for each individual group entry.The following example illustrates how to do this.

Suppose the input file looks like:



01 DATA-RECORD. 05 IDENTIFIER PIC X(8). 05 ACTION-COUNT PIC S9(4) COMP. 05 ACTIONS OCCURS 0 TO 12 TIMES DEPENDING ON ACTION-COUNT. 10 DATE PIC X(8). 10 TYPE PIC X. 10 AMT PIC S9(11)V99 COMP-3.

To get individual records for this group, you need to add the “SEPARATE”parameter to the #GROUPBEG like:

#RECORD V 10 202IDENTIFIER X 0 8 AACTION-COUNT B 8 2 O#GROUPBEG 10 ACTION-COUNT SEPARATEDATE X 0 8 ATYPE X 8 1 AAMT P2 9 7 9.#GROUPEND#END

Without the word “SEPARATE” on the #GROUPBEG, the converted outputcould look like:

DAVE,08/02/93,A,345.22,08/03/93,A,333.67,08/04/93,D,22.00

With the word “SEPARATE: on the #GROUPBEG, the converted outputwould then look like:

DAVE,08/02/93,A,345.22DAVE,08/03/93,A,333.67DAVE,08/04/93,D,22.00

SEPARATE implies that data preceding the group will be repeated on eachseparated output record.



#CRLF

The CRLF statement causes a carriage-return/line-feed pair to be immediatelyinserted into the output file.

#CRLF

Any buffered output accumulated up to now (see #SKIP below) will be placed inthe output file before the carriage- return/line-feed pair. This statement allowsyou to produce two or more output records for a single input record.



#INSERT Literal

This statement allows you to imbed a literal into the output data stream.

#INSERT literal

literal

Is one or more characters of data. The literal may containimbedded spaces. All data from the line beginning with“#INSERT” will be moved to the output file. The literal maycontain hexadecimal characters - see “Character Strings” belowfor more information.

Example

Suppose our script was something like this:

• • •rec-type X 44 1 O#if rec-type = A handleA#if rec-type = D handleD#insert CHG#goto continue@handleA#insert ADD#goto continue@handleD#insert DEL@continuedate-@ X 45 8 A"time-2 P2 53 3 9. • • •

The relevant portion of the output file might look like this:

... ,ADD,"08/03/93",24.55 ...

... ,ADD,"08/03/93",214.95 ...

... ,DEL,"08/04/93",11.12 ...

... ,CHG,"08/05/93",33.45 ...



#LINE

The statement allows you to insert an entire line of data into the output file.

#LINE literal

literal

Is one or more characters of data. The literal may containimbedded spaces. All data from the line beginning with“#LINE” will be immediately moved to the output file.

The literal may contain hexadecimal characters - see “CharacterStrings” below for more information.

The inserted line will be written to the output file immediately. This line will beplaced ahead of any data currently being converted for this logical input record.

Example

Suppose we have a script looking like:

DATE X 0 8 AFIELD2 X 8 1 A#IF FIELD2 <> B CONTINUE#LINE B-RECORD Follows@CONTINUETIME X 9 8 A#END

And furthermore, suppose there are three input logical records of which the thirdhas a 'B' in “FIELD2.” Then, the output looks something like:

08/07/93,A,21:00:0308/08/93,A,22:00:17B-RECORD Follows08/09/93,B,17:22:46

Notice how the inserted line precedes the third output record even though it wasspecified between “FIELD2” and “TIME” in the script above.



#END

This statement indicates the end of script processing for the current input logicalrecord. Converted data will be followed by a carriage-return/line-feed pair. Theprocessor will then adjust its input pointers to the next logical input record andbegin processing again at the beginning of the script.

#END

All scripts must have a #END as the last line. It must also begin in column 1.



#SKIP Record

As a script file is processed, the converted output is held in an internal buffer.Converted output data is not actually committed to the output file until one ofthree things happens:

1) an #END statement is encountered,

2) a #CRLF statement is encountered, or

3) the internal buffer is exceeded, in which case the data currently in the bufferis written to the output file and processing continues with the next fieldidentified in the script. BIMFCV uses a 2K internal buffer. The host scriptprocessor (BIMFTRXP) uses a 30K internal buffer.

The #SKIP statement differs from the #END statement above in that datacontained in this internal buffer is not written to the output file.

#SKIP

Special Requirements for BIMFCV

Unlike the Host Script processor (BIMFTRXP), BIMFCV does not know whereeach record ends, and the next one starts. It relies entirely on the #RECORD,#GROUPBEG and #GROUPEND statements to define each record. You mustensure that these statements appear in your script, and are processed by thescript prior to any #SKIP statement.



Putting it all together

The examples that follow should help you understand how to use the FileConversion Script language.

(1) - A Simple Fixed Length Record File

01 DATA-RECORD. 05 TRANSACTION-CODE PIC X. 88 ADD-TRANSACTION VALUE 'A'. 88 DEL-TRANSACTION VALUE 'D'. 88 CHG-TRANSACTION VALUE 'C'. 05 ACCOUNT-NO PIC 9(11) COMP-3. 05 ACCOUNT-NAME PIC X(30). 05 TRANSACTION-DATE PIC X(8). 05 TRANSACTION-AMT PIC S9(7)V99 COMP-3.

Is scripted as:

#RECORD F 50TRANSACTION-CODE X 0 1 AACCOUNT-NO P 1 6 9ACCOUNT-NAME X 7 30 A'TRANSACTION-DATE X 37 8 ATRANSACTION-AMT P2 45 5 9.#END

Suppose for a moment that all we wanted to convert were “ADD-TRANSACTION” records. Our script then becomes:

#RECORD F 50TRANSACTION-CODE X 0 1 A* We test to see if this is an ADD-TRANSACTION#IF TRANSACTION-CODE = A KEEPIT* If not an ADD-TRANSACTION, we skip the record#SKIP* We get here if and when TRANSACTION-CODE = 'A'@KEEPITACCOUNT-NO P 1 6 9ACCOUNT-NAME X 7 30 A'TRANSACTION-DATE X 37 8 ATRANSACTION-AMT P2 45 5 9.#END

Now suppose we want all records, but we want to change the order of fieldsaround a bit and we don't care about “TRANSACTION-DATE.” Our script mightthen be:



#RECORD F 50ACCOUNT-NO P 1 6 9TRANSACTION-CODE X 0 1 ATRANSACTION-AMT P2 45 5 9.ACCOUNT-NAME X 7 30 A'#END

In this last instance, we did not include TRANSACTION-DATE in the scriptbecause we didn't want it included in the output. We could also have placed itanywhere in the script like:

TRANSACTION-DATE X 37 8 O

This would have the same effect as omitting it. Omitting the field definitionworks fine until we get to group processing (see below for additionalconsiderations).



(2) - A variable file containing multiple record types

01 DATA-RECORD. 05 RECORD-KEY PIC X(16). 05 RECORD-TYPE PIC X. 05 RECORD-AREA. 10 NAME PIC X(30). 10 ADDRESS-1 PIC X(30). 10 ADDRESS-2 PIC X(30). 10 CITY PIC X(25). 10 STATE PIC XX. 10 ZIP PIC 9(9) COMP-3. 05 FILLER REDEFINES RECORD-AREA. 10 CURRENT-AMT PIC S9(11)V99. 05 FILLER REDEFINES RECORD-AREA. 10 WITHDRAWAL PIC S9(11)V99. 10 DATE PIC X(8). 10 TIME PIC X(8).

Its script becomes:

#RECORD V 24 139RECORD-KEY X 0 16 ARECORD-TYPE X 16 1 A#IF RECORD-TYPE = A AddressRec#IF RECORD-TYPE = C CurntAmt#IF RECORD-TYPE = W Withdrawal#ERROR Bad Record Type@AddressRec#RECORD F 139NAME X 17 30 AADDRESS-1 X 47 30 AADDRESS-2 X 77 30 ACITY X 107 25 ASTATE X 132 2 AZIP P 134 5 9#END@CurntAmt#RECORD F 24CURRENT-AMT P2 17 7 9.#END@Withdrawal#RECORD F 40WITHDRAWAL P2 17 7 9.TIME X 32 8 A#END

Notice how at each label, the record format is redefined. This is how the scriptprocessor determines the logical record length.



Files Containing a COBOL OCCURS DEPENDING ON clause

Special considerations apply when dealing with files of this type. A few examplesshould suffice to illustrate the requirements.

(1) - A file containing an OCCURS DEPENDING ON

01 DATA-RECORD. 05 ACCOUNT-NUM PIC 9(12). 05 SUMMARY-COUNT PIC S9(4) COMP. 05 SUMMARY-DATA OCCURS 0 TO 100 TIMES DEPENDING ON SUMMARY-COUNT. 10 SUMMARY-TRAN PIC X. 10 SUMMARY-DATE PIC X(8). 10 SUMMARY-AMT PIC S9(11)V99 COMP-3.

The File Conversion Script looks like:

#RECORD V 14 174ACCOUNT-NUM Z 0 12 9SUMMARY-COUNT B 12 2 9#GROUPBEG 14 SUMMARY-COUNTSUMMARY-TRAN X 0 1 A* we don't want date on the output file, but* need to include it within the groupSUMMARY-DATE X 1 8 O*SUMMARY-AMT P2 9 7 9.#GROUPEND#END

This is the trivial case. The only thing unusual in the above is that we did notwant field “SUMMARY-DATE” to go on the converted file. The field, or at least aplace holder of some kind, must be contained within the variably occurringgroup for the script processor to be able to determine the correct length of thegroup. Both goals are achieved by using a convert of “O” for the field.



(2) - OCCURS DEPENDING ON within an OCCURS DEPENDING ON

01 DATA-RECORD. 05 SOME-STUFF PIC X(30). 05 TABLE-1_COUNT PIC S9(4) COMP. 05 TABLE-1 OCCURS 0 TO 100 TIMES DEPENDING ON TABLE-1-COUNT. 10 T1-ITEM PIC X(8). 10 T1-AMT PIC S(5)V99 COMP-3. 10 TABLE-2-COUNT PIC S9(4) COMP. 10 TABLE-2 OCCURS 0 TO 12 TIMES DEPENDING ON TABLE-2-COUNT. 15 T2-ITEM PIC X(8).

The File Conversion Script looks like:

#RECORD V 32 1142SOME-STUFF X 0 30 ATABLE-1-COUNT B 30 2 9#GROUPBEG 32 TABLE-1-COUNTT1-ITEM X 0 8 AT1-AMT P2 8 4 9.TABLE-2-COUNT B 12 2 9#GROUPBEG 14 TABLE-2-COUNTT2-ITEM X 0 8 A#GROUPEND#GROUPEND#END

Here, the variable entry “TABLE-1” is itself of variable length. Note how theoffsets within both groups reverts to zero with each #GROUPBEG statement.Notice also that the offset for the second group is known to be 14 - that is 14 bytesfrom the beginning of the first group.



(3) OCCURS DEPENDING ON followed by OCCURS DEPENDING ON

01 DATA-RECORD. 05 PRELIMINARY PIC X(10). 05 T1-COUNT PIC S9(4) COMP. 05 T2-COUNT PIC S9(4) COMP. 05 TABLE-1 OCCURS 0 TO 100 TIMES DEPENDING ON T1-COUNT. 10 T1-ITEM-1 PIC X(8). 10 T1-ITEM-2 PIC X(8). 05 TABLE-2 OCCURS 0 TO 100 TIMES DEPENDING ON T2-COUNT. 10 T2-ITEM-1 PIC X(4). 10 T2-ITEM-2 PIC X.

The File Conversion Script becomes:

#RECORD V 14 2114PRELIMINARY X 0 10 AT1-COUNT B 10 2 9T2-COUNT B 12 2 9#GROUPBEG 14 T1-COUNTT1-ITEM-1 X 0 8 AT1-ITEM-2 X 8 8 A#GROUPEND#GROUPBEG * T2-COUNTT2-ITEM-1 X 0 4 AT2-ITEM-2 X 4 1 A#GROUPEND#END

The second group must use the asterisk for its offset. This is required since thereis no way to predict where it will begin without examining the individual record.The offsets with the second group, however, do start off from zero since theseoffsets are relative to the beginning of the group.



Processing ASCII Files

ASCII files (perhaps a downloaded report from the mainframe) can be processedusing BIMFCV and a File Conversion Script. Special considerations apply whenprocessing an ASCII file.

1. You must specify the “ASCII” option to the script processor (see Executingthe Program for more information).

2. An ASCII file consists of a series of text line terminated by a carriage-return/line-feed (CRLF) pair. The “ASCII” option instructs the scriptprocessor to consider each text line as a logical record and to dynamicallydetermine the line length by looking for the trailing CRLF.

3. ASCII files typically contain one or more blank lines. The “ASCII” optioninstructs the script processor to bypass lines containing nothing but spaces.Only lines containing non-blank characters will be examined.

4. Reports (possibly downloaded from the mainframe) typically containheading lines. You will need to exercise your creativity, but you can easilybypass these lines (the example below shows one way to do it).

Consider the following sample ASCII file which contains a short reportcontaining some information about the solar system.

Distance from Year Diameter Mass Sun (mi) (in days) (mi) (Earth = 1) ------------- ------- ------ --------

Mercury 36,000,000 88 3,031 0.0600Venus 67,230,000 225 7,520 0.8200Earth 92,960,000 365 7,926 1.0000Mars 141,700,000 687 4,200 0.1100Jupiter 483,700,000 4,333 88,700 318.0000Saturn 885,200,000 10,759 74,600 95.0000Uranus 1,781,000,000 30,685 31,570 14.6000Neptune 2,788,000,000 60,188 30,200 17.2000Pluto 3,660,000,000 90,700 1,900 0.0017

Suppose further that we want to convert the report to comma delimited stringscontaining only the data - we don't want the two heading lines, we don't want theblank line (automatically removed), and we want to remove the commas fromthe numeric data in the report. The File Definition Script below will fulfill ourrequirements.



#RECORD F 132chek1 X 10 8 Ochek2 X 12 3 O** Check for and remove heading lines*#IF chek1 = Distance SKIPIT#IF chek2 = Sun SKIPIT#IF chek1 = -------- SKIPIT*planet X 0 7 N* +---- Convert = 'N'* (already ASCII)*dist X 10 13 Eyear X 27 6 Ediameter X 37 6 Emass X 47 8 E* +---- Convert = 'E'* (kills leading* spaces)#END*@SKIPIT#SKIP

NOTES:

1. Strictly speaking the #RECORD statement would not be needed since theASCII option causes the script processor to dynamically determine linelengths. However, the script processor demands a #RECORD statement bepresent in each script so we must include one here also.

2. Fields “chek1” and “chek2” are sufficient to identify and remove all threeheading lines. Field “chek1” is used to identify both the 1st and 3rd headingline, while field “chek2” will handle the 2nd heading line. The #IFstatements show you how it was done.

3. The planet name needs no conversion since it is already in ASCII. Using anyof the “A” conversion options will cause strange results for this field.

4. Each numeric field uses the “E” conversion option. This option will removethe commas from the numeric values and also eliminates leading spaces.We would not need to use the “E” option for the last field, “mass”, but itwas included to cause leading spaces to be absorbed.



Using this script resulted in the following output file (actual test data andresults):

Mercury,36000000,88,3031,0.0600Venus ,67230000,225,7520,0.8200Earth ,92960000,365,7926,1.0000Mars ,141700000,687,4200,0.1100Jupiter,483700000,4333,88700,318.0000Saturn ,885200000,10759,74600,95.0000Uranus ,1781000000,30685,31570,14.6000Neptune,2788000000,60188,30200,17.2000Pluto ,3660000000,90700,1900,0.0017

Always remember to specify the ASCII option when processing ASCII files.



Character Strings

Character strings containing imbedded spaces must be enclosed within quotes.You can use either single quotes (') or double quotes (").

Hexadecimal Characters in BIMFCV Scripts

Character strings that are entered in the #IF, #INSERT and #LINE statementsmay contain hexadecimal characters. Any hexadecimal value may be enteredexcept for binary zeros (X'00').

This support is not available in scripts processed by the Host Script Processor(BIMFTRXP).

Hexadecimal data is indicated by the backslash ('\').

Commonly occurring hex bytes have been abbreviated.

\e -or- \E ESC X'1B'

\n -or- \N line-feed X'0A'

\r -or- \R carriage-return X'0D'

\\ backslash

Other hexadecimal values are entered as \xx, where the xx are the hexadecimalequivalents for the desired character.

For example, \7E will be converted to a tilde ('~').



Testing Your Script

BIM-PC/TRANSFER offers limited assistance for testing your script files. BIMrecommends that you work with a subset of your input file to ease the testingprocess.

It is possible for BIM-PC/TRANSFER to get confused as it attempts to processthe input file. While attempts have been made to detect this, it is not alwayspossible. BIMFCV will close the output file on errors it detects. You can thenexamine the output to see the last good conversion and begin your search forproblems in the script from that point.

Unfortunately, BIM-PC/TRANSFER can on occasion get completely lost in itsattempt to traverse an input record. This may result in a lock up of the PC andultimately in a re-boot to clear up the situation. This arises in large part due tothe fact that BIM-PC/TRANSFER is not able to determine record lengths in anyway other than by trusting the File Conversion Script. The potential problem isexacerbated by variable length records (those containing a COBOL OCCURSDEPENDING ON clause).

Should BIMFCV become terribly confused, it won't be able to close the output fileand you won't be able to look at it to get a starting point for the problem. You cansupply an optional command line argument to help in this situation.

bimfcv input output script DEBUG

This becomes the 4th argument on the PC command line. It causes BIMFCV towrite each converted record to the PC screen as well as the disk file.

Hopefully, you should be able to see where BIMFCV got confused by analyzingthe PC display.


Page 306 Driver Specifications

Driver SpecificationsThe following sections provide specific rules and considerations for using each ofthe DRIVERs supplied by BIM-PC/TRANSFER.

Driver Page

BIMFTRD$ - IND$ Driver (VSE Only) 307

BIMFTRDB - VSE Library Driver (VSE/ESA 1.2 and above Only) 310

BIMFTRDC - VSAM Cluster Driver 315

BIMFTRDD - Partitioned Dataset Driver (MVS Only) 328

BIMFTRDE - BIM-EDIT Library Driver 330

BIMFTRDF - BIM-EPIC and SAM Dataset Driver (VSE Only) 337

BIMFTRDI - ICCF Library Driver (VSE Only) 345

BIMFTRDJ - JES Access Driver (MVS Only) 347

BIMFTRDL - VSE Library Driver (VSE Only) 351

BIMFTRDM - CICS Temporary Storage Access 354

BIMFTRDP - POWER Queue Driver (VSE Only) 356

BIMFTRDQ - Sequential (QSAM) Dataset Driver (MVS Only) 362

BIMFTRDR - VSE Library Access Using BIM-EDIT (VSE Only) 365

BIMFTRDT - CICS Transient Data Upload Driver 368

BIMFTRDV - VSAM Dataset Driver (Using Profiles) 370

BIMFTRDX - Script File Access 375


Driver Specifications (BIMFTRD$ - IND$) Page 307

BIMFTRD$ - IND$ Driver (VSE Only)

This driver is used to upload to and download from the IBM Host Transfer File.This driver is not supported when using BIM-TMAN for the host side of BIM-PC/TRANSFER, or for CICS releases prior to 2.2.

This driver requires a TWASIZE of 256 to be defined on the transaction definitionfor ‘FTRT’.

The use of a formatting / selection exit is required if you wish to upload data tothe IBM Host Transfer File unless the data uses CRLFs to separate records, or theLRECL option is used when requesting the transfer on the PC.

Signon Requirements The PC user must be signed on to the VSEInteractive Interface prior to attempting anytransfers. The USER ID used on the PC mustalso match the one used for the IUI signon.

Uploads Supported YES

Downloads Supported YES

Upload NEW Supported YES

Upload REPLACE Supported YES

Upload APPEND Supported NO

EXIT Supported Uploads and Downloads

CRLF Default Y

TRANSLATE Default Y

LRECL Default if CRLF=N isspecified and LRECL is notspecified by the PC

Actual record length for download, 0 forupload

Download Selection Dialog Fields

The following fields will be presented on the PC in a dialog box when adownload is requested for this driver. These fields are used to specify whichmember(s) should be presented in the PC File Transfer Window. Fields that areleft blank will not be used for selection processing.


Page 308 (BIMFTRD$ - IND$) Driver Specifications

Field NameMaxlen. Type Kwd Description

FileName 8 char NAM Filename of the requestedmember(s) in the IND$ HostTransfer File. If left blank, allmembers will be selected. (SeeStatus field below.)

FileType 8 char TYP File Type of the requestedmember(s) in the IND$ HostTransfer file.

Owner 8 char OWN Owner of the requested member(s).Status 3 char STA Status of the desired members:

* All membersPub Public members onlyPrv Private members onlyShr Shared members onlyThis driver will only selectmembers that the PC user isauthorized to see, that is, membersthat are owned by the PC user, orare declared public or shared forthe PC user.

Download ScriptName

16 char SCP Specifies a File Conversion Scriptname to be used for the download.This name must match a scriptdefined to the Host.

Upload Dialog Fields

The following fields will be presented on the PC in a dialog box when a upload isrequested for this driver. These fields are used to specify the name andcharacteristics of the member to be uploaded:


FileName 8 char NAM Filename of the member in theIND$ Host Transfer File. Defaultsto the PC filename

FileType 8 char TYP File Type of the member in theIND$ Host Transfer file. Defaults tothe PC filename extension.

Status 3 char STA Status of the member:Pub Public memberPrv Private member


Driver Specifications (BIMFTRD$ - IND$) Page 309

DRIVER DATA

The following DRIVER DATA fields can be specified to customize the processingof this Driver:

*** BIM-PC/TRANSFER *** CATEGORY DEFINITION yyyy/mm/dd hh:mm:ss

DRIVER DATA: filename pgmname notifyus notifyow ________ ________ ________ ________ ________ ________ ________ ________

Note: DRIVER DATA fields are ‘positional’. All options that you specify inthese fields must be specified in the exact field positions shown above.

filename

This is the name of the CICS FCT entry for the Host Transfer File. The default isINWFILE.

pgmname

This is the name of the application interface module for the Host Transfer File.The default is INWMAPI.

notifyus

Specify NOTIFYUS in the third DRIVER DATA position to cause all shared usersof a Host Transfer File to be notified when a file is uploaded.

notifyow

Specify NOTIFYOW in the forth DRIVER DATA position to cause the owner of aHost Transfer File to be notified when a file is downloaded.


Page 310 (BIMFTRDB - VSE Library) Driver Specifications

BIMFTRDB - VSE Library Driver (VSE/ESA 1.2 and above Only)

This driver is used to download members and upload members to a VSE Libraryusing the VSE/ESA LIBRM interface.

The LIBRM interface used by this driver requires VSE/ESA 1.2 or above. Youmust also be using release 1.5.0.0 or above of the BIM-PC/TRANSFER PCprogram. If you are running older releases than these, you must use driverBIMFTRDL or BIMFTRDR for VSE Library Access.

This driver attaches a VSE subtask to the CICS or BIM-TMAN partition for theduration of each transfer. The subtask is used to perform the LIBRM requestsagainst the VSE Library. This is done to protect your online system from LIBRabends that may occur, and to allow the CICS multi-tasking environment tofunction properly. There will be a separate subtask for each transfer in progress.

Signon Requirements None





Upload APPEND Supported YES

EXIT Supported Downloads only

CRLF Default See Processing Default Table below

TRANSLATE Default See Processing Default Table below


80


Driver Specifications (BIMFTRDB - VSE Library) Page 311

Processing Default Table

This driver contains an internal table that it uses to determine defaults for CRLF,TRANSLATE and 'Record Format'. The defaults selected are based on the 'Type'assigned to the VSE library member being transferred.

Type TRANSLATE CRLF Record FormatBIN No No ByteCOM No No ByteDLL No No ByteDOC No No ByteDUMP No No ByteE No No ByteEXE No No ByteHTM Yes Yes RecordHTML Yes Yes RecordOBJ No No RecordPHASE No No BytePROC Yes Yes RecordRTF Yes Yes RecordTXT Yes Yes RecordWPD No No ByteXLS No No ByteXLW No No Byte

All other member 'Types' will have the following defaults, based on the specified'Record Format'.

Record Format Translate CRLFByte No NoRecord Yes Yes






Library.Sublib 16 char LIB Required. This is the VSE libraryand sub-library to be searched forthe desired members. If the sublibis specified as a generic value, aspecial list box will be generated onthe PC containing all matchingsublibs in the specified library. ThePC user can than select the specificsublib to be used.

Member 8 char MEM Generic name of the requestedmember(s).

Type 8 char TYP Generic type of the requestedmember(s). This is the source type,A, C, OBJ, etc.

Download Defaults/Options Dialog Fields

The following fields will be presented on the PC in a dialog box when either the“Defaults” button is pressed on the “Download Selection Dialog”, or the“Category Options” button is pressed on a “Download Destination Dialog” forthis driver.

The “Defaults” dialog is used to provide default processing options for allselected entries. The “Options” dialog is used to override processing options forspecific downloads.


Download ScriptName


Truncate TrailingBlanks

3 char TRB Specifies whether or not trailingblanks should be truncated fromeach host record.Can be ‘No’, or ‘Yes’.‘No’ means don’t truncate trailing

blanks.‘Yes’ means truncate trailing

blanks. This is the default.


Driver Specifications (BIMFTRDB - VSE Library) Page 313




Library.Sublib 16 char LIB Required. This is the VSE libraryand sub-library into which themember is to be loaded. If thesublib is specified as a genericvalue, a special list box will begenerated on the PC containing allmatching sublibs in the specifiedlibrary. The PC user can than selectthe specific sublib to be used

Member 8 char MEM Name of the member. If omitted,the PC filename is used.

Type 8 char TYP Type of the member. This is thesource type, A, C, OBJ, etc. Ifomitted, the PC filename extensionis used.

Data in PROC 1 char DAT This field is only used if the Typefield is PROC. It indicates whetherthe procedure contains data withinit. This field must be specified asYes or No. Default is 'No', for nodata in procedure.

Record Format 6 char RFM This field indicates how the data isto be stored in the VSE Library.This field can be specified as:Record The data is to be stored as

a series of 80-byte records.Byte The data is to be stored as

a continuous string ofbytes.

* Use the default from the"Processing Default Table"described above.



Truncate LongRecords

3 char TRC Specifies what action should occurif a PC record exceeds the maxallowed for the VSE Librarymember.Can be 'Yes' or 'No'.'No' means to cancel the transfer.

This is the default.'Yes' means to truncate the long

record(s).

DRIVER DATA



DRIVER DATA: mshp ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________


mshp

Specify 'MSHP' in this position if you want this Category Definition to be able toupload to VSE Library members that are under control of MSHP. If this option isnot specified, these attempts will be rejected with message BIMFTRDB-12.


Driver Specifications (BIMFTRDC - VSAM Clusters) Page 315

BIMFTRDC - VSAM Cluster Driver

This driver is used to upload records to and download records from VSAMclusters. The cluster name to be transfered, and for VSE, the catalog it iscontained in, is specified by the PC user as part of the upload or downloaddialog.

You cannot use this driver to transfer VSAM clusters that are defined to CICS viaindividual FCT entries. Driver BIMFTRDV can be used to transfer those datasets.

This driver does not make use of BIM-PC/TRANSFER "VSAM Profiles". If youneed to perform VSAM transfers using features contained in a "VSAM Profile",use driver BIMFTRDV.

KSDS, RRDS and variable length or fixed-unblocked ESDS datasets can beuploaded or downloaded. Uploads require the use of a formatting / selection exitunless:


• The data from the PC is separated into records with CRLFs.

Fixed-Blocked ESDS datasets are only supported if the host side of BIM-PC/TRANSFER is being executed in BIM-TMAN. CICS does not support accessto Fixed-Blocked ESDS datasets.

If you are uploading to a fixed length VSAM dataset, without an exit, and the PCrecords are separated with CRLFs, then all PC records must be the length definedfor the VSAM dataset unless the PAD and/or TRUNCATE Driver Data optionsare used.

For uploads from the PC, existing records are read and updated by key, or newrecords are added by key. If you want the entire file replaced, refer to the EMPTYDriver Data option below.


Uploads Supported YES (may require an EXIT)


Upload NEW Supported NO at the file level, YES at the VSAM recordlevel. (See EMPTY Driver Data Option)

For VSE, Upload NEW is supported at thefile level if the IDCAMS Driver Data optionis used, and an IDCAMS Definition isprovided by the PC user.


Page 316 (BIMFTRDC - VSAM Clusters) Driver Specifications

Upload REPLACE Supported YES (at the VSAM record level).

For VSE, Upload REPLACE is supported atthe file level if the IDCAMS Driver Dataoption is used, and an IDCAMS Definition isprovided by the PC user.



CRLF Default Y

TRANSLATE Default Y


Actual record length for download, fixedrecord length for upload unless EXIT isused.


The following fields will be presented on the PC in a dialog box when adownload is requested for this driver. These fields are used to specify whichVSAM clusters should be presented in the PC File Transfer Window. Fields thatare left blank will not be used for selection processing.


Cluster Name 44 char DSN Specifies the VSAM Cluster Nameto be transferred. If this is specifiedas a generic value, all matchingclusters from the catalog will beshown in the available itemssection. For MVS, a generic valuemust include the high-levelqualifier.

Catalog DLBLName

8 char CAT (VSE Only) Specifies the DLBLname of the catalog in which theCluster Name is cataloged. If leftblank, the VSAM Master Catalog isassumed.

Cluster Type 4 char TYP Used to qualify selection to VSAMclusters for a specific type. Can be:'*' for all, KSDS, ESDS, RRDS, orSAM (VSE only).




The following field will be presented on the PC in a dialog box when either the“Defaults” button is pressed on the “Download Selection Dialog”, or the“Category Options” button is pressed on a “Download Destination Dialog” forthis driver.



Download ScriptName


Upload Dialog Fields (when IDCAMS Driver Data Option not specified)

The following fields will be presented on the PC in a dialog box when a upload isrequested for this driver and the IDCAMS Driver Data Option has not beenspecified. These fields are used to specify which already defined VSAM cluster isto be used for the upload:


Cluster Name 44 char DSN Specifies the VSAM Cluster Nameto be transferred to. If this isspecified as a generic value, aspecial list box will be generated onthe PC containing all matchingclusters from the catalog. The PCuser can than select the specificcluster to be used. For MVS, ageneric value must include thehigh-level qualifier.

Catalog DLBLName




Upload Dialog Fields (when IDCAMS Driver Data Option is specified)

The following fields will be presented on the PC in a dialog box when a upload isrequested for this driver and the IDCAMS Driver Data Option has beenspecified. These fields are used to specify which VSAM cluster is to be used forthe upload:


Cluster Name 44 char DSN Specifies the VSAM Cluster Nameto be transferred to. If this isspecified as a generic value, aspecial list box will be generated onthe PC containing all matchingclusters from the catalog. The PCuser can than select the specificcluster to be used. For MVS, ageneric value must include thehigh-level qualifier.

Catalog DLBLName


IDCAMSDelete/Define

16 char IDC (VSE Only) Specifies the name ofan IDCAMS Definition containedin the BIM-PC/TRANSFER hostcontrol file that is to be processedprior to opening the specifiedVSAM cluster.This field is ignored if the specifiedcluster already exists in the VSAMcatalog, and an Upload APPENDhas been specified.

The remaining fields are ignored if the IDCAMS Delete/Define field is notspecified.



Record Format 8 char RFM (VSE Only) Specifies the recordformat for the VSAM cluster beingdefinedThis determines the values for the%RECSZ, %AVGSZ, and%SAMRECFM script variables.Valid values are: 'Fixed', 'Variable',and 'Undef'.The default is 'Fixed'.'Undef' is only valid for SAM-ESDS.

Max/Fixed Recsize 5 Num LRL (VSE Only) Specifies the maximumor fixed record size for the VSAMcluster being defined.This determines the values used forthe %RECSZ, %AVGSZ,%SAMMAXSZ and %SAMAVGSZscript variables.A default and maximum allowedvalue can be specified in theIDCAM Definition via the#RECSZ= statement.

Nbr Records toAlloc.

8 Num NRA (VSE Only) Specifies the number ofrecords to allocate space for.This determines the value used forthe %NRECS script variables.A default and maximum allowedvalue can be specified in theIDCAM Definition via the#NRECS= statement.

Blk Factor forSAM-ESDS

5 Num BLK (VSE Only) Specifies the blockingfactor for files with a RecordFormat of 'Fixed'.This determines the values used forthe %SAMMAXSZ and%SAMAVGSZ script variables.The default is 1, which defines thefixed format file as 'unblocked'.

DRIVER DATA





DRIVER DATA: bim$dn0 bim$up0 truncate PADhh catdd fxexit empty idcams ________ ________ ________ %DRVD


bim$dn0

This option is only used if the host component of BIM-PC/TRANSFER is runningin CICS. It is not used when running in BIM-TMAN. Specify the name of theCICS FCT entry to be used to access the VSAM clusters during downloads. Ifomitted, BIM$DN0 is assumed. Any value you specify here must begin with"BIM$" and must be defined to CICS. Refer to "CICS Considerations" below formore information.

bim$up0

This option is only used if the host component of BIM-PC/TRANSFER is runningin CICS. It is not used when running in BIM-TMAN. Specify the name of theCICS FCT entry to be used to access the VSAM clusters during uploads. Ifomitted, BIM$UP0 is assumed. Any value you specify here must begin with"BIM$" and must be defined to CICS. Refer to "CICS Considerations" below formore information.

truncate

Specify TRUNCATE in this field if you want the driver to truncate any uploadedrecords that are larger than the maximum allowed for the defined VSAM cluster.If this option is omitted, message BIMFTRDC-12 will be generated if a larger thanallowed record is detected.

PADhh

Specify PAD in this field if you want the driver to pad any uploaded records thatare shorter than what is defined for a fixed-length VSAM dataset. 'hh' is the hexvalue to be used as the pad character. 'PAD40' will pad the record with spaces. Ifthis option is omitted, message BIMFTRDC-12 will be generated if a shorter thanallowed record is detected.

catdd

(VSE only). Specify the DLBL of the VSAM catalog to be used as a default for alltransfer requests that do not specify a catalog name. If omitted, the VSE VSAMMaster Catalog will be used.

fxexit

Specify name of a formatting/selection exit to be invoked for all transfers usingthis category definition.



empty

Specify EMPTY in this field if you want the driver to open reusable VSAM ESDSfiles (or VSAM-managed SAM for VSE) with the EMPTY option during uploadsthat specify the “REPLACE” option for REPLACE/NEW/APPEND. This optionis ignored if the upload request specifies the “NEW” or “APPEND” option.

idcams

(VSE Only) Specify IDCAMS in this field if you want to enable the IDCAMSDelete/Define processing fields in the Upload Dialog presented to the PC userfor this Category.

%DRVD

The contents of this field are used to replace any reference to variable '%DRVD'.Refer to the section “Dataset Access Definition Screen” on page 221 for moreinformation.

CICS Considerations for Driver BIMFTRDC:

You must define at least two CICS FCT entries. One for uploads on one fordownloads. The FCT names must match the values defined for Driver Dataoptions 'bim$up0' and 'bim$dn0'.

Do not include a DLBL or DD in your CICS JCL for these FCT entries. BIM-PC/TRANSFER will automatically generate the DLBL/DD for each transfer,using the specific VSAM Cluster name and UCAT specified on the PC.

The following FCT entries are examples of what is required. These are includedin source member BIMFTRS1 and for MVS, RDO DEFINEs are contained inBIMFTRJ3:

BIM$UP0 DFHFCT TYPE=DATASET, X DATASET=BIM$UP0, X FILSTAT=(UNENABLED,CLOSED), X ACCMETH=(VSAM), X SERVREQ=(READ,UPDATE,ADD,BROWSE,DELETE), X RECFORM=(VARIABLE,BLOCKED),LSRPOOL=NONE, X STRNO=2BIM$DN0 DFHFCT TYPE=DATASET, X DATASET=BIM$DN0, X FILSTAT=(UNENABLED,CLOSED), X ACCMETH=(VSAM), X SERVREQ=(READ,BROWSE), X RECFORM=(VARIABLE,BLOCKED),LSRPOOL=NONE, X STRNO=2

For newer releases of CICS, the FCT entry must be defined withFILSTAT=(UNENABLED,CLOSED). If your CICS release does not supportUNENABLED, then use FILSTAT=(ENABLED,CLOSED). BIM-PC/TRANSFERwill automatically open and close the dataset for each transfer. The FCT entriesmust also be defined with a RECFORM of (VARIABLE,BLOCKED). BIM-



PC/TRANSFER will automatically handle fixed length VSAM clusters based oninformation contained in the VSAM catalog.

BIM-PC/TRANSFER will ENQUEUE on the FCT name, thus single-threading thetransfer.

If the seventh position of the BIM$XXn name is numeric and greater than zero,BIM-PC/TRANSFER will assume that multiple FCT entries have been provided,and will search for the first non-busy FCT entry for use during the transfer.

If you specify the name as BIM$UP3, it will be assumed that you have providedFCT entries with names: BIM$UP0, BIM$UP1, BIM$UP2 and BIM$UP3. Thisallows up to 10 FCT entries, and thus 10 concurrent transfers.

BIM-TMAN Considerations for Driver BIMFTRDC:

No file definitions or JCL are required.Transfers are not single-threaded as theyare in CICS.

IDCAMS Definitions

IDCAMS Definitions are only supported in VSE.

IDCAMS Definitions can be specified during an Upload to enable dynamicdefinitions of VSAM clusters. This feature is enabled by specifying the 'idcams'Driver Data options described above.

IDCAMS Definitions are defined and maintained in the BIM-PC/TRANSFERhost control file (BIMFTRF) as 'Script Definitions'.

The IDCAMS commands are processed by module BIMFTR98. (New for release1.8 of BIM-PC/TRANSFER). Module BIMFTR98 attaches a VSE subtask whichCDLOADs IDCAMS, and processes the commands. The VSE subtask is used onlyfor the duration of the IDCAMS processing, at which time it is terminated. TheVSE subtask is used to protect your online system from IDCAMS abends thatmay occur, and to allow the CICS multi-tasking environment to functionproperly. There will be a separate subtask for each transfer concurrentlyperforming and IDCAMS Delete/Define.

IDCAMS Definition Syntax

IDCAMS Definition 'scripts' must be in the following format:

• The first line of the 'script' must contain the value #IDCAMS in columns 1-7.

• Following the #IDCAMS line, and prior to the first IDCAMS command areplaced any #keyword= statements described below.

• Following any #keyword= statements are the actual IDCAMS commands toDelete/Define the desired cluster.

• The last line of the 'script' must contain the value #END in columns 1-4.



• You can enter the commands in either upper or lower case, or anycombination. The samples below show the #keyword commands and%variables in lower case for clarity only.

Refer to the Sample IDCAMS Definitions below.

#keyword Commands

Several commands can be provided in your IDCAMS Definition Script to controlhow the IDCAMS commands are generated. Most of these commands are used toinfluence the values used for the 'IDCAMS Script Variables' described below.

The syntax of these commands is as show below. Each command must appear ona line by itself. The '#' must appear in column 1, and no spaces can be includedexcept as shown below.

The following #keyword commands can be used:

#MAXCC=mmmmm

This command provides the maximum allowed return code fromIDCAMS that is to be assumed by BIM-PC/TRANSFER to be asuccessful completion. The default is zero. If a return codegreater than this value is returned, the transfer will not beperformed, and error BIMFTR98-6 will be generated.

#RECSZ=nnnnn,mmmmm

This command provides a default (nnnnn) and amaximum(mmmmm) value for the 'Max/Fixed Recsize' fieldsupplied by the PC user. The default is used if the PC user leavesthe field blank. An error (BIMFTR98-13) is generated if the PCuser specifies a value large than the max (mmmmm).

#NRECS=nnnnn,mmmmm

This command provides a default (nnnnn) and amaximum(mmmmm) value for the 'Nbr Records to Alloc.' fieldsupplied by the PC user. The default is used if the PC user leavesthe field blank. An error (BIMFTR98-14) is generated if the PCuser specifies a value large than the max (mmmmm).

#VOL=catdnm(volser1 … volsern)

This command specifies the value for the %VOL script variable,based on the VSE Catalog DLBL name (catdnm) entered by thePC user. Specify a separate #VOL command for each catalog thatcan be used for this script.

If one or more #VOL commands appear in a script, then onlythose specified catalogs will be valid.



IDCAMS Script Variables

Several 'variables' have been defined that can be used in your IDCAMS scripts toenable them to be tailored to the specific VSAM cluster being transferred.

Syntax: %varname

If you need to include a '%' in your script that is not part of a script variable, youmust specify it twice:

%%NAME would appear as %NAME in the command passed to IDCAMS.

The following variables can be specified:

%DLBL This variable represents the DLBL name generated by BIM-PC/TRANSFER for the VSAM cluster being uploaded.

%CLUSTER This variable contains the 'Cluster Name' specified by the PCuser.

%CATDNM This variable contains VSE Catalog DLBL name entered by thePC user. If no value is specified by the PC user, this variabledefaults to either IJSYSUC or IJSYSCT depending on which oneis found in the JCL.

%CATDSN This variable contains the VSE Catalog 'Cluster Name' from theDLBL for variable %CATDNM.

%VOL This variable contains the volume(s) to use. This is retrievedfrom a #VOL command that contains a 'catdnm' that matches%CATDNM.

%RECSZ This variable contains the value from the 'Max/Fixed Recsize'field from the PC user, or the default from the #RECSZ=command.

%AVGSZ This variable contains a calculated 'Average Record Size'. If thespecified Record Format is 'Fixed', then this field is set to thesame value as %RECSZ, otherwise it is set to 50% of the %RECSZvalue.

BIM-PC/TRANSFER requires 'Fixed' format VSAM clusters tobe defined with the average and maximum record sizes thesame, and 'Variable' format VSAM clusters to be defined withdifferent values for average and maximum.

%NRECS This variable contains the value from the 'Nbr Records to Alloc.'field from the PC user, or the default from the #NRECS=command.

%NRECS50 This variable contains a calculated value of 50% of the value in%NRECS, rounded down. This can be used for specification of asecondary allocation value.





The remaining script variables are only useful when defining a SAM-ESDScluster:

%SAMRECFM This variable contains a value for the IDCAMSRECORDFORMAT operand of a SAM-ESDS Cluster. It isgenerated based on the values of 'Record Format' and 'BlkFactor':

Record Format Blk Factor =1 Blk Factor > 1Fixed F FB(%RECSZ)

Variable VB VB

Undefined U U

%SAMAVGSZ This variable contains a value for the 'average' value of theIDCAMS RECORDSIZE operand of a SAM-ESDS Cluster. It isgenerated based on the values of 'Record Format' and 'BlkFactor':

Record Format Blk Factor =1 Blk Factor > 1Fixed %RECSZ Calculated

Blocksize

Variable %AVGSZ %AVGSZ

Undefined %AVGSZ %AVGSZ

%SAMMAXSZ This variable contains a value for the 'maximum' value of theIDCAMS RECORDSIZE operand of a SAM-ESDS Cluster. It isgenerated based on the values of 'Record Format' and 'BlkFactor':

Record Format Blk Factor =1 Blk Factor > 1Fixed %RECSZ Calculated

Blocksize

Variable %RECSZ %RECSZ

Undefined %RECSZ %RECSZ

Sample IDCAMS Definition (ESDS)

This sample shows how a typical ESDS cluster can be defined using substitutionvariables and #keyword statements to control processing.

In this example, the default record size will be 256, the maximum allowed will be1024. The default number of records to allocate will be 50, the maximum 1000.Only definitions in catalogs 'BIMUCAT' or 'IJSYSCT' will be allowed.



#IDCAMS#recsz=256,1024#nrecs=50,1000#vol=bimucat(DSK50C)#vol=ijsysct(DSKC01 DSKC02 DSKC03);PARM SYNCHKDELETE (%cluster) PURGE CLUSTER - CATALOG(%catdsn)IF LASTCC = 8 THEN SET MAXCC = 0DEF CL ( NAME(%cluster) - VOLUMES(%vol) - NONINDEXED SPEED SHAREOPTION(2) RECORDS(%nrecs %nrecs10) - RECORDSIZE(%avgsz %recsz) ) - DATA( NAME(%cluster.DATA) ) - CATALOG(%catdsn)#END

If a transfer was requested for cluster 'TEST.ESDS.FILE' in catalog BIMUCAT,with a Record Format of 'Variable', a Max Record Size of 500, and a number ofrecords to allocate of 200, the following IDCAMS commands would be executed:

DELETE (TEST.ESDS.FILE) PURGE CLUSTER - CATALOG(BIM.USER.CATALOG)IF LASTCC = 8 THEN SET MAXCC = 0DEF CL ( NAME(TEST.ESDS.FILE) - VOLUMES(DSK50C) - NONINDEXED SPEED SHAREOPTION(2) RECORDS(200 20) - RECORDSIZE(250 500) ) - DATA( NAME(TEST.ESDS.FILE.DATA) ) - CATALOG(BIM.USER.CATALOG)

Sample IDCAMS Definition (SAM-ESDS)

This sample shows how a typical SAM-ESDS cluster can be defined usingsubstitution variables and #keyword statements to control processing.

In this example, the default record size will be 80, the maximum allowed will be256. The default number of records to allocate will be 50, the maximum 1000.Only definitions in catalogs 'BIMUCAT' or 'IJSYSCT' will be allowed.



#IDCAMS#recsz=80,256#nrecs=50,1000#vol=bimucat(DSK50C)#vol=ijsysct(DSKC01 DSKC02 DSKC03);PARM SYNCHKDELETE (%cluster) PURGE CLUSTER - CATALOG(%catdsn)IF LASTCC = 8 THEN SET MAXCC = 0DEF CL ( NAME(%cluster) - VOLUMES(%vol) - RECORDFORMAT(%samrecfm) RECORDSIZE(%samavgsz %sammaxsz) - NONINDEXED SPEED SHAREOPTION(2) RECORDS(%nrecs %nrecs25) ) - DATA (NAME(%cluster.DATA)) - CATALOG(%catdsn)#END

If a transfer was requested for cluster 'TEST.SAMESDS.FILE' in catalog IJSYSCT,with a Record Format of 'Fixed', a Fixed Record Size of 80, a blocking Factor of10, and a number of records to allocate of 200, the following IDCAMS commandswould be executed:

DELETE (TEST.SAMESDS.FILE) PURGE CLUSTER - CATALOG(VSAM.MASTER.CATALOG)IF LASTCC = 8 THEN SET MAXCC = 0DEF CL ( NAME(TEST.SAMESDS.FILE) - VOLUMES(DSKC01 DSKC02 DSKC03) - RECORDFORMAT(FB(80)) RECORDSIZE(800 800) - NONINDEXED SPEED SHAREOPTION(2) RECORDS(200 50) ) - DATA (NAME(TEST.SAMESDS.FILE.DATA)) - CATALOG(VSAM.MASTER.CATALOG)


Page 328 (BIMFTRDD - PDS) Driver Specifications

BIMFTRDD - Partitioned Dataset Driver (MVS Only)

This driver is used to upload members to and download members from an MVSPartitioned Dataset.

This driver requires that the PDS be an existing cataloged dataset. The datasetcan have a RECFM of F, FB, or VB, and must have an LRECL not greater than29900.

This driver uses the “Dataset Access Definitions” defined in the “UserDefinition” for access authorization to specific Partitioned Datasets.








CRLF Default Y

TRANSLATE Default Y


Actual record length for downloads, 80 foruploads.




PDS Dataset Name 44 char DSN Required. This is the PDS name tobe searched for the desiredmembers. If this is specified as ageneric value, a special list box willbe generated on the PC containingall matching PDS datasets from thecatalog. The PC user can than selectthe specific PDS to be used. Ageneric PDS must include the high-level qualifier.


Driver Specifications (BIMFTRDD - PDS) Page 329

PDS Member 8 char MEM Generic name of the requestedmember(s).

Download ScriptName



The following fields will be presented on the PC in a dialog box when a upload isrequested for this driver. These fields are used to specify the name of the memberto be uploaded:


PDS Dataset Name 44 char DSN Required. This is the PDS namethat the member is to be loadedinto. It must be the name of acataloged partitioned dataset. Ifthis is specified as a generic value,a special list box will be generatedon the PC containing all matchingPDS datasets from the catalog. ThePC user can than select the specificPDS to be used. A generic PDSmust include the high-levelqualifier.

PDS Member 8 char MEM Name of the member in the PDS. Ifomitted, the PC filename is used.

DRIVER DATA



DRIVER DATA: ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ %DRVD


%DRVD



Page 330 (BIMFTRDE - BIM-EDIT) Driver Specifications

BIMFTRDE - BIM-EDIT Library Driver

This driver is used to upload members to and download members from a BIM-EDIT Library. This driver can also be used to access BIM-EDIT mail items bysetting a special Driver Data Option.

Signon Requirements The USER ID and PASSWORD used on thePC must be defined to BIM-EDIT. Thisdriver will logon to BIM-EDIT prior toperforming the transfer.







CRLF Default Y

TRANSLATE Default Y


Actual line length for downloads, 253 foruploads.

Download Selection Dialog Fields (for EDIT members)



Library 16 char LIB Required. This is the BIM-EDITlibrary name to be searched for thedesired members. If this isspecified as a generic value, aspecial list box will be generated onthe PC containing all matchingBIM-EDIT libraries. The PC usercan than select the specific libraryto be used.

Member 16 char MEM Name of the requested member(s).Type 8 char TYP Type of the requested member(s).

This is the BIM-EDIT member type.


Driver Specifications (BIMFTRDE - BIM-EDIT) Page 331

Title 40 char TTL BIM-EDIT Title. This will normallyrequire a generic specification.Refer to the section “DownloadSelection Dialog” on page 97 for adescription of generic.

Attr 8 char ATT ATTR of the requested member(s).This is the BIM-EDIT memberATTR field.

Download Defaults/Options Dialog Fields (for EDIT members)




Download ScriptName


Expand Includes 3 char INC Specifies how BIM-EDIT shouldhandle /INCLUDE statements.Can be ‘*’, ‘No’, or ‘Yes’.‘*’ means use ‘incl’ driver dataoption setting.‘No’ means don’t expand/INCLUDE statements.‘Yes’ means expand /INCLUDEstatements.

TRAP Processing 3 char TRP Can be ‘No’, or ‘Yes’.‘Yes’ means that TRAP=ON shouldbe specified on the BIM-EDITSEND command.

VariableSubstitution

3 char VBL Can be ‘No’, or ‘Yes’.‘Yes’ means that VBL=ON shouldbe specified on the BIM-EDITSEND command.

HEX Replacement 3 char HEX Can be ‘No’, or ‘Yes’.‘Yes’ means that HEX=ON shouldbe specified on the BIM-EDITSEND command.



Upload Dialog Fields (for EDIT members)



Library 16 char LIB Required. This is the BIM-EDITlibrary that the member is toloaded into. If this is specified as ageneric value, a special list box willbe generated on the PC containingall matching BIM-EDIT libraries.The PC user can than select thespecific library to be used.


Type 8 char TYP BIM-EDIT member Type. Ifomitted, the PC filename extensionis used.

Title 40 char TTL BIM-EDIT member Title.Attr 8 char ATT BIM-EDIT member ATTR.Case 1 char CAS Case of member in BIM-EDIT:

M Mixed (default)U Upper (member text will

be translated to upper case)Checkout 3 char CHK BIM-EDIT checkout control (On or

Off).Nulls 3 char NUL BIM-EDIT Nulls control (On or

Off).Libdef 8 char LDF BIM-EDIT Libdef member field.User 8 char USR BIM-EDIT User member field.



Download Selection Dialog Fields (for EDIT mail items)

The following fields will be presented on the PC in a dialog box when adownload is requested for this driver when the 'MAIL' Driver Data option is set.These fields are used to specify which mail items should be presented in the PCFile Transfer Window. Fields that are left blank will not be used for selectionprocessing.


From User 8 char USR This is the BIM-EDIT user id of thesender of the desired mail item(s).

Type of Mail 4 char TYP Type of mail that is requested:'New', 'Old', or 'Both'.

'New' mail is the BIM-EDIT'Incoming Mail'.

'Old' mail is the BIM-EDIT 'Mail SetAside'.

Title 40 char TTL BIM-EDIT mail Title. This willnormally require a genericspecification. Refer to the section“Download Selection Dialog” onpage 97 for a description of generic.

Download Defaults/Options Dialog Fields (for EDIT mail items)

The following fields will be presented on the PC in a dialog box when either the“Defaults” button is pressed on the “Download Selection Dialog”, or the“Category Options” button is pressed on a “Download Destination Dialog” forthis driver when the 'MAIL' Driver Data option is set.



Discard AfterDownload

3 char DEL This option specifies whether ornot the mail item should bediscarded after being sent to thePC: No/Yes. The default is No.



Upload Dialog Fields (for EDIT mail items)

The following fields will be presented on the PC in a dialog box when a upload isrequested for this driver when the 'MAIL' Driver Data option is set. These fieldsare used to specify the name and characteristics of the member to be uploaded:


To User 8 char USR Required. This is the BIM-EDITuser id of the receiver of the mail.

Title 40 char TTL BIM-EDIT mail Title.ACK Option 3 char ACK Specifies whether or not the BIM-

EDIT ACK option should bespecified on the mail item.'No' or 'Yes'. Default is 'No'.

DRIVER DATA



DRIVER DATA: lu62/svc bimedit lu62unit lu62lmod lu62appl inclmail checkout library checkin header ________ ________


lu62/svc

Specify LU62 in this field if you want to use the LU 6.2 interface to BIM-EDIT.For VSE, leave this field blank if you want to use the XPCC interface. For MVS,you can leave this field blank if you used the default SVC number in MVSInstallation Step 2. If you used a different SVC number, specify the value here inthe format 'SVCnnn' where 'nnn' is the SVC number you used. Refer to the BIM-EDIT System Reference Manual for more information on the LU 6.2 interface.

bimedit

This field contains the BIM-EDIT system name. The default is BIMEDIT. If youhave more than one BIM-EDIT system, you can specify the name of the desiredsystem here.

lu62unit

This field is used for the LU 6.2 interface to BIM-EDIT. It contains the LogicalUnit name to be used for the connection to BIM-EDIT. The default is BIMAPPL.



lu62lmod

This field is used for the LU 6.2 interface to BIM-EDIT. It contains the Logmodename to be used for the connection to BIM-EDIT. The default is EDITLU62.

lu62appl

This field is used for the LU 6.2 interface to BIM-EDIT. It contains the APPLname to be used for the connection to BIM-EDIT. The default is BIMEDIT.

inclmail

Specify INCL in this field if you want BIM-EDIT includes (/INCL) to beexpanded during downloads.

Specify MAIL in this field if you want this Category Definition to process BIM-EDIT mail items.

The 'MAIL' and 'INCL' options are mutually exclusive.

checkout library

These two fields are used to supply the name of a BIM-EDIT library to be usedfor a CHECKOUT of members being transferred to the PC. If these fields are leftblank, no CHECKOUT will be performed.

The CHECKOUT will only be performed if the member being downloaded isdefined to BIM-EDIT as being under checkout control.

checkin

This field must contain the word CHECKIN if you want this driver toautomatically CHECKIN BIM-EDIT members after they have been transferredfrom the PC to the mainframe. If this field is left blank, but a 'checkout library'has been specified, uploaded members will be sent to the 'checkout library' andleft there for a future manual CHECKIN command to be issued from within BIM-EDIT.

The CHECKIN will only be performed if the member being uploaded is definedto BIM-EDIT as being under checkout control.

header

This field must contain the word HEADER if you want this driver to insertseveral lines at the beginning of each downloaded member, containing thecurrent BIM-EDIT member attributes. The first and last generated line containsthe value '$$PCFTR$$'. The lines in between contain BIM-EDIT ALTERcommands.

During uploads of these members, the ALTER commands are passed to BIM-EDIT to define the uploaded member with all of the same attributes as theoriginal member.



When using this feature, the attributes of the Upload dialog on the PC areignored.


Driver Specifications (BIMFTRDF - BIM-EPIC and SAM) Page 337

BIMFTRDF - BIM-EPIC and SAM Dataset Driver (VSE Only)

This driver is used to upload records to and download records from either a VSESAM dataset or a BIM-EPIC managed dataset.

Datasets can contain records and/or blocks up to 32000 bytes in length. Recordformats can be Fixed, Fixed-Blocked, Variable-Length, or Undefined. This driverdoes not support spanned format records.

The BIM-EPIC managed dataset support requires BIM-EPIC release 6.1B at PTFlevel EP61B041 or above. It also requires a CICS PPT or RDO definition forprogram 'BIMEPACC'.

This driver attaches a VSE subtask to the CICS or BIM-TMAN partition for theduration of each transfer. The subtask is used to perform the OPEN, CLOSE,GET, PUT, and TRUNC requests against the dataset. This is done to protect youronline system from VSE abends that occur for I/O errors. There will be a separatesubtask for each transfer in progress.




Upload NEW Supported NO




CRLF Default Y

TRANSLATE Default Y




Page 338 (BIMFTRDF - BIM-EPIC and SAM) Driver Specifications

SAM versus EPIC Processing Mode

This driver can run in one of two processing modes:

SAM This processing mode is used to process either VSE SAM datasets orBIM-EPIC managed datasets using "SAM Profiles". This mode isactivated by specifying 'SAM' in the first Driver Data field of a"Category Definition" defined for this driver.

EPIC This processing mode is used to process only BIM-EPIC manageddatasets. This mode does not use SAM Profiles. This mode isactivated by specifying 'EPIC' in the first Driver Data field of a"Category Definition" defined for this driver.

The topics that follow describe the Upload and Download Dialogs that arepresented to the PC user for each of these processing modes.

BIM-EPIC Start Track 1 Dataset Support

You can upload to datasets not defined in the BIM-EPIC catalog if the followingconditions are met:

1) The 'strack1' Driver Data option is set.

2) 'Start Track 1' support is active in your BIM-EPIC system.

3) The PC user specifies a STrack1 Pool Name and Extent Size in the UploadDialog.

If any of these conditions is not met, then only BIM-EPIC managed datasets canbe uploaded.

Once you have uploaded to a Start Track 1 dataset, you will only be able todownload that dataset if the BIM-EPIC system option CATRT1=YES was activewhen the upload occurred. This option will cause BIM-EPIC to automaticallycatalog the new dataset.



Download Selection Dialog Fields (SAM mode)

The following fields will be presented on the PC in a dialog box when adownload is requested for this driver when in SAM processing mode. Thesefields are used to specify which SAM Profiles should be presented in the PC FileTransfer Window. Fields that are left blank will not be used for selectionprocessing.


SAM Profile 16 char PRO This is a generic mask describingthe SAM Profile name(s) thatshould be listed. If this field is leftblank, all SAM Profiles will belisted. Refer to the section“Download Selection Dialog” onpage 97 for a description of generic.

Dataset Name 44 char DSN This is a generic mask describingthe DLBL dataset name(s) or theBIM-EPIC DSN(s) desired.

Profile Description 40 char DSC This is a generic mask describingthe SAM Profile Description of thedesired profiles.

Download Defaults/Options Dialog Fields (SAM mode)

The following fields will be presented on the PC in a dialog box when either the“Defaults” button is pressed on the “Download Selection Dialog”, or the“Category Options” button is pressed on a “Download Destination Dialog” forthis driver when in SAM processing mode.



Download ScriptName



3 char TRB Specifies whether or not trailingblanks should be truncated fromeach host record.Can be ‘*’, ‘No’, or ‘Yes’.‘*’ means use driver data optionsetting.‘No’ means don’t truncate trailingblanks.



‘Yes’ means truncate trailingblanks.

Upload Dialog Fields (SAM mode)

The following fields will be presented on the PC in a dialog box when a upload isrequested for this driver when in SAM processing mode:


SAM Profile 16 char PRO Required. This is the name of theSAM Profile to be used for theupload.

Download Selection Dialog Fields (EPIC mode)

The following fields will be presented on the PC in a dialog box when adownload is requested for this driver when in EPIC processing mode. Thesefields are used to specify which BIM-EPIC catalog entries should be presented inthe PC File Transfer Window. Fields that are left blank will not be used forselection processing.


Dataset Name 44 char DSN Specifies the BIM-EPIC manageddataset name to be transferred. Ifthis is specified as a generic value,all matching entries from the BIM-EPIC catalog will be shown in theavailable items section.

Version Number 4 num VER Specifies the desired BIM-EPICversion number of a generationdataset.

GenerationNumber

6 num GEN Specifies the desired BIM-EPICgeneration number.

Creation Job Name 8 char CJN Specifies the name of the job thatcreated the dataset.

Minimum Age inHours

5 num HRL Specifies the minimum age the filecan be, in hours since creation.

Maximum Age inHours

5 num HRM Specifies the maximum age the filecan be, in hours since creation.

Last Access JobName

8 char AJN Specifies the name of the job thatlast accessed the dataset.

Generations 5 char GNS Specifies which generation(s)should be selected for processing.This option will normally be usedin an Automatic Transfer Script.This option can be:"All" - select all generations. They



will be displayed newest to oldest."First" - select the first/newestgeneration."Last" - select the last/oldestgeneration.

EPIC CommentField

30 char COM This is a generic mask describingthe required contents of thecomment field in the BIM-EPICcatalog record.

Download Defaults/Options Dialog Fields (EPIC mode)

The following fields will be presented on the PC in a dialog box when either the“Defaults” button is pressed on the “Download Selection Dialog”, or the“Category Options” button is pressed on a “Download Destination Dialog” forthis driver when in EPIC processing mode.



New Last AccessJob Name

8 char UPJ Specifies a new value to be placedin the BIM-EPIC catalog for the lastaccessed job name. This is onlydone if the transfer completesnormally.This option can only be specified ifthe 'Update' Driver Data Optionhas been specified.

Delete Datasetafter Download

3 char DEL Specifies whether or not the datasetshould be deleted after a successfultransfer. Can be 'No' or 'Yes'. Thedefault is 'No'.This option can only be specified ifthe 'Delete' Driver Data Option hasbeen specified.


3 char TRB Specifies whether or not trailingblanks should be truncated fromeach host record.Can be ‘No’ or ‘Yes’.‘No’ means don’t truncate trailingblanks.‘Yes’ means truncate trailingblanks.



Download ScriptName


Record Format 6 char RFM Specifies the record format fordatasets that don't have the formatdefined in the BIM-EPIC catalog.Can be "Fixblk", "Undef", "Varblk".

Recsize for Fixblk 5 num LRL Specifies the record size for fixedlength datasets that don't have thesize defined in the BIM-EPICcatalog.

MaximumBlocksize

5 num BLK Specifies the block size for datasetsthat don't have the size defined inthe BIM-EPIC catalog.

Upload Dialog Fields (EPIC mode)

The following fields will be presented on the PC in a dialog box when a upload isrequested for this driver when in EPIC processing mode:


Dataset Name 44 char DSN Required. This is the name of thedataset to be created.

Record Format 6 char RFM Specifies the record format of thedataset.Can be "Fixblk", "Undef", "Varblk".

Recsize for Fixblk 5 num LRL Specifies the record size for fixedlength datasets. Can be any valueup to 32000.

MaximumBlocksize

5 num BLK Specifies the maximum block sizefor Varblk and Undef files, or theactual blocksize for Fixblk files.Can be any value up to 32761.

Truncate LongRecords

3 char TRC Specifies whether what actionshould occur if a PC record exceedsthe maximum allowed for thedataset.Can be ‘*’, ‘No’, or ‘Yes’.‘*’ means use driver data optionsetting. (This is the default.)‘No’ means cancel the transfer.‘Yes’ means truncate the PC record.

Pad Short Records 5 char PAD Specifies whether what actionshould occur if a PC record is less



that the defined record size for afixed length file.Can be ‘*’, ‘No’, ‘Space', or 'Null'.‘*’ means use driver data optionsetting. (This is the default.)‘No’ means cancel the transfer.‘Space’ means pad the PC recordwith spaces'Null' means pad the PC recordwith binary zeros.

STrack1 PoolName

6 char XPN This option can be used if the'strack1' driver data option hasbeen specified, and you want toupload to a dataset that is notdefined in the BIM-EPIC catalog.This option also requires that 'StartTrack 1' dataset support is active inyour BIM-EPIC system.This field specifies the Pool namedefined to BIM-EPIC where thisdataset should be allocated.

STrack1 ExtentSize

5 num XSZ This is used in conjunction with thePool Name field above to specifythe initial allocation for the dataset.

DRIVER DATA



DRIVER DATA: epic/sam strack1 truncate PADhh delete update ________ ________ ________ ________ ________ ________


epic/sam

Specifies the processing mode for this Category Definition. If anything other than'EPIC' is specified, then 'SAM' is assumed.

strack1

Specify STRACK1 in this field if you want to allow uploads to BIM-EPIC StartTrack 1 datasets. This option is only valid when in the EPIC processing mode.



truncate

Specify TRUNCATE in this field if you want the driver to truncate any uploadedrecords that are larger than the maximum allowed for the dataset.

PADhh

Specify PAD in this field if you want the driver to pad any uploaded records thatare shorter than what is defined for the dataset. 'hh' is the hex value to be used asthe pad character. 'PAD40' will pad the record with spaces.

delete

Specify DELETE in this field if you want to allow the PC user to specify that thedataset should be deleted after a successful download. This option is only validwhen in the EPIC processing mode.

update

Specify UPDATE in this field if you want to allow the PC user to specify that theLast Access Job Name field in the BIM-EPIC catalog should be updated after asuccessful download. This option is only valid when in the EPIC processingmode.


Driver Specifications (BIMFTRDI - ICCF) Page 345

BIMFTRDI - ICCF Library Driver (VSE Only)

This driver is used to download members from an ICCF Library. BIM-PC/TRANSFER does not support uploads directly to ICCF.


Uploads Supported NO



Upload REPLACE Supported NO



CRLF Default Y

TRANSLATE Default Y


80




Library 3 num LIB Required. This is the ICCF librarynumber to be searched for thedesired members.

Member 8 char MEM Name of the requested member(s).User 4 char USR User of the requested member(s).

This is the ICCF member user field.Download ScriptName



Page 346 (BIMFTRDI - ICCF) Driver Specifications

DRIVER DATA



DRIVER DATA: dtsfile ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________


dtsfile

This is the DLBL name for the ICCF Library. The default is DTSFILE.


Driver Specifications (BIMFTRDJ - JES) Page 347

BIMFTRDJ - JES Access Driver (MVS Only)

This driver is used to upload jobs to and download reports from JES.

JCL is uploaded to the JES internal reader for execution.

Reports can be downloaded from either the JES Output or Held queues. They canbe downloaded by Job output class, or individual SYSOUT DD.


Uploads Supported YES to the JES internal reader





EXIT Supported Downloads Only

CRLF Default Y

TRANSLATE Default Y


80 for uploads, 132 for downloads, 133 fordownloads if 'CC' driver data option used.


The following fields will be presented on the PC in a dialog box when adownload is requested for this driver. These fields are used to specify whichreports(s) should be presented in the PC File Transfer Window. Fields that areleft blank will not be used for selection processing.


Queue 6 char Q Required. JES Queue. Can be'Output' or 'Held'.

Job Name 8 char JNM Generic name of the requestedreports(s).

Job ID 8 char JID Generic JES job ID. (JOBnnnnn,STCnnnnn, TSUnnnnn).

Job Output Class 1 char CLS JES Output Class of the requestedreport(s).

Job Output Group 8 char GRP JES Output Group of the requestedreport(s).

Owner 8 char OWN Generic TSO Userid that submittedthe report(s).


Page 348 (BIMFTRDJ - JES) Driver Specifications

Destination 8 char DST Generic DEST for the requestedreport(s).

Programmer 20 char PRO Generic value contained in theprogrammer field of the requestedreport(s).

Query by 6 char QBY Specifies the type of query:Job request all output for

job.DDname output by DD.Both Both of the above.

DDname 8 char DDN Generic DDname for Query byDDname and Class.

Step Name 8 char STP Generic Stepname for Query byDDname and Class.

ProcStep Name 8 char PST Generic Procedure Stepname forQuery by DDname and Class.





Download ScriptName


Printer CC In Data 3 char DCC Specifies the carriage controlprocessing option.Can be ‘*’, ‘No’, or ‘Yes’.‘*’ means use ‘cc’ driver data optionsetting.‘No’ means send each line of thereport to the PC, with each linefollowed by a standard CRLF.‘Yes’ means that the actual carriagecontrol characters are to be passedto the PC in the first position ofeach line.


Driver Specifications (BIMFTRDJ - JES) Page 349


The following fields will be presented on the PC in a dialog box when a upload isrequested for this driver.:


Queue 6 char Q Required. JES Queue. Must be'IRDR'.

DRIVER DATA



DRIVER DATA: SVCnnn jobname claslist cc delete $c owner ________ ________ ________ ________ ________


SVCnnn

If you used the default SVC number in MVS Installation Step 2, you can leavethis field blank. If not, specify the SVC number you selected as the 'nnn' in theSVCnnn field.

jobname

If you want to restrict the access to JES reports, you can specify a genericjobname mask in this field. Only jobs that match this mask will be presented fordownloads. If you specify this field as '$USER', then only jobs that begin with thePC users ID will be presented.

claslist

This field can contain up to 8 classes. If specified, only JES reports contained inone of these Job Classes will be presented for download.

cc

If you specify 'CC' in this field, the reports carriage control will be downloadedas the first position of each data line. If this field is left blank, only the report datawill be transmitted.

delete

If you specify 'DELETE' in this field, the report will be purged from the JESqueue following a successful download. Please note that BIM-PC/TRANSFERalways purges an entire “Job Output Element” (JOE) in JES.


Page 350 (BIMFTRDJ - JES) Driver Specifications

$c

If you specify 'DELETE' in the previous field, then this field is used for the JEScommand to be used to delete the reports. If this field is left blank, ‘$C’ isassumed.

owner

If you want to restrict the access to JES reports, you can specify a generic 'owner'mask in this field. Only jobs with 'owners' that match this mask will be presentedfor downloads. If you specify this field as '$USER', then only jobs that weresubmitted with the PC users ID will be presented.


Driver Specifications (BIMFTRDL - LIBR) Page 351

BIMFTRDL - VSE Library Driver (VSE Only)

This driver is used to download members and upload members to a VSE Libraryusing the LIBR interface.

If you are running VSE/ESA 1.2 or above, you will probably want to use driverBIMFTRDB instead of this one. Refer to page 310 for more information.

This driver requires the use of a LIBR server program (BIMFTRLB) running in abatch partition (either dynamic or static). The following JCL can be used toinitiate the server:

* $$ JOB JNM=BIMFTRLB,CLASS=C,DISP=L// JOB BIMFTRLB BIM-PC/TRANSFER LIBR SERVER// LIBDEF PHASE,SEARCH=(lib.sublib)// EXEC BIMFTRLB,SIZE=(AUTO,145K)START IDENT(BIMFTRLB)/*/&* $$ EOJ

There are two ways to terminate the server task:

1) Submit a jobstream like the above with the parameter 'STOP' instead of'START'.

2) Enter 'MSG pp' from the console, where 'pp' is the partition runningBIMFTRLB and respond STOP to the prompt message.

Each LIBR server task can perform one transfer at a time. If you want to run morethan one transfer at a time, you can initiate multiple server jobstreams, each in aseparate partition. Each server task will wait for a transfer request from BIM-PC/TRANSFER, perform the request, and resume waiting.

BIM-PC/TRANSFER communicates to the LIBR server task(s) using the VSEXPCC interface. Therefore, the CICS or BIM-TMAN running BIM-PC/TRANSFER must be in the same VSE machine as the LIBR server task(s).

Refer to the DRIVER DATA section below for an automated startup option forthe LIBR task.








Page 352 (BIMFTRDL - LIBR) Driver Specifications


CRLF Default OBJ, PHASE, E, and DUMP types default to'N', all others default to 'Y'.

TRANSLATE Default (same as CRLF default)


80




Library.Sublib 16 char LIB Required. This is the VSE libraryand sub-library to be searched forthe desired members. If the sublibis specified as a generic value, aspecial list box will be generated onthe PC containing all matchingsublibs in the specified library. ThePC user can than select the specificsublib to be used.


This is the source type, OBJ, etc.Download ScriptName





Library.Sublib 16 char LIB Required. This is the VSE libraryand sub-library into which themember is to be loaded. If thesublib is specified as a genericvalue, a special list box will begenerated on the PC containing allmatching sublibs in the specified


Driver Specifications (BIMFTRDL - LIBR) Page 353

library. The PC user can than selectthe specific sublib to be used


Type 8 char TYP Type of the member. This is thesource type, OBJ, etc. If omitted,the PC filename extension is used.

Data in PROC 1 char DAT This field is only used if the Typefield is PROC. It indicates whetherthe procedure contains data withinit. This field must be specified as Yor N, for yes/no. Default is 'N'. forno data in procedure.

DRIVER DATA



DRIVER DATA: jobname nnnn ident stop ________ ________ ________ ________ ________ ________ ________ ________


jobname

This is the name of a jobstream in the POWER RDR queue that should bereleased if it is determined that the LIBR server task is not running. The default isto return an error condition to the PC.

nnnn

This is the interval, in seconds, that BIM-PC/TRANSFER should wait for the'jobname' to activate the LIBR server before returning an error to the PC. Thisvalue must be entered as a 4-digit number. The default is 0005.

ident

This is the IDENT name used in the VSE XPCC interface to communicate withthe LIBR server. The default is BIMFTRLB. If you cannot use the default name,you must use the same name here, and in the IDENT parameter of the LIBRserver startup JCL shown above.

stop

Enter STOP in this field if you want the batch LIBR server task to be shutdownafter each transfer is completed. If this is not specified, the job will be leftexecuting in a 'wait' state for the next request.


Page 354 (BIMFTRDM - Temporary Storage) Driver Specifications

BIMFTRDM - CICS Temporary Storage Access

This driver is used to download lines from and upload lines to a CICSTemporary Storage Queue.







EXIT Supported NO

CRLF Default 'Y'

TRANSLATE Default 'Y'


Actual TS item length for downloads, 30,000for uploads.


The following fields will be presented on the PC in a dialog box when adownload is requested for this driver. These fields are used to specify whichTemporary Storage Queue should be presented in the PC File Transfer Window.Fields that are left blank will not be used for selection processing.


TS Queue Name 8 char TSQ Required. This is the name of thedesired Temporary Storage Queue.

Sysid 4 char SID CICS System ID of the systemowning the Temporary StorageQueue. This field is ignored if youare using BIM-TMAN instead ofCICS. If this field is left blank, theexecuting CICS System ID isassumed.

Purge afterdownload

3 char PUR Yes/No. Specifies whether or notthe Temporary Storage Queueshould be purged from CICS afterthe download. The default is 'No'.


Driver Specifications (BIMFTRDM - Temporary Storage) Page 355




TS Queue Name 8 char TSQ Required. This is the name of thedesired Temporary Storage Queue.

Type of Storage 4 char STG Aux/Main. Specifies the type ofCICS Temporary Storage to use.The default is 'Aux'. This field isignored if you are using BIM-TMAN instead of CICS.

Sysid 4 char SID CICS System ID of the systemowning the Temporary StorageQueue. This field is ignored if youare using BIM-TMAN instead ofCICS. If this field is left blank, theexecuting CICS System ID isassumed.

DRIVER DATA

This driver does not use any of the DRIVER DATA fields.

CICS ENQ/DEQ Feature

This driver will ENQ on the Temporary Storage Queue prior to beginning eachtransfer. This can be used to prevent access by multiple applications and/ortransfers functions. When each transfer is completed, a DEQ is issued.

The actual ENQ resource is 16 bytes long, and has the following format:

BIMFTRDMqqqqqqqq

where 'qqqqqqqq' is the 8-byte Temporary Storage Queue name.

Any attempt to perform a transfer while an ENQ is active will result in messageBIMFTRDM-6 being returned to the PC.


Page 356 (BIMFTRDP - POWER) Driver Specifications

BIMFTRDP - POWER Queue Driver (VSE Only)

This driver is used to download or upload jobstreams or reports in the POWERRDR, LST, and PUN queues using the POWER XPCC interface.








CRLF Default Y

TRANSLATE Default Y


132 for LST queue, 80 for RDR and PUNqueues. If the CC driver option is used, thedefaults are 133 and 81.




Queue 3 char Q Required. This is the POWERQueue to be searched for thedesired jobs/reports. Must be LST,RDR, or PUN.

Job/Report Name 8 char JNM Name of the requestedjobs/reports.

Job/ReportNumber

5 num JNO Job number of the requestedjob/report (cannot be generic).

Class 4 char CLS Required. Specify up to 4 POWERclasses to be searched in therequested queue.

Disposition 1 char DSP POWER job/report disposition.Can be 'D', 'H','K' or 'L'.

Priority 1 num PRI POWER job/report priority. Can be0 through 9.


Driver Specifications (BIMFTRDP - POWER) Page 357

Remote-ID 3 num REM POWER job/report Remote ID.Can be 0 through 255.

Destination Node 8 char DN POWER job/report DestinationNode.

Destination User 8 char DU POWER job/report DestinationUser ID.

User Information 16 char USR POWER job/report USER field.Form 4 char FRM POWER job/report FNO field.System ID 1 num SYS POWER job/report SYSID.Suffix 3 num SFX POWER job/report suffix for a

segment of a large report.





Download ScriptName


Printer CC In Data 4 char DCC Specifies the carriage controlprocessing option.Can be ‘*’, ‘No’, ‘Yes’, ‘APF’, ‘ASA’,or ‘Data’.'*' means use 'ccoption' driver dataoption setting.'No' means carriage control is to beconverted to CRLF’s, NL’s, andFF’s, based on the reports FCB.‘Yes’ means that the actual carriagecontrol characters are to be passedto the PC in the first position ofeach line.



'ASA' means convert the carriagecontrol characters to ASA, and passthem to the PC in the first positionof each line.‘Data’ means ignore the FCB andcarriage control in the report, andsend each line of the report to thePC, with each line followed by astandard CRLF.‘APF’ means that the report is in aspecial format for advancedfunction printers.




Queue 3 char Q Required. This is the POWERQueue that the PC member is to beloaded into. Must be LST, RDR, orPUN.Uploads to the RDR queue requirevalid POWER JECL.

Job/Report Name 8 char JNM Name of the job/report. If omitted,the PC filename is used.

Class 1 char CLS Required. Specifies the class to beassigned to the uploaded member.

Disposition 1 char DSP POWER job/report disposition.Can be 'D', 'H','K' or 'L'.

Priority 1 num PRI POWER job/report priority. Can be0 through 9.

Remote-ID 3 num REM POWER job/report Remote ID.Can be 0 through 255.

Copy Count 3 num CC POWER job/report Copy Count.Can be 1 through 999.

Destination Node 8 char DN POWER job/report DestinationNode.

Destination User 8 char DU POWER job/report DestinationUser ID.

User Information 16 char USR POWER job/report USER field.Form 4 char FRM POWER job/report FNO field.System ID 1 num SYS POWER job/report SYSID.



FCB 8 char FCB FCB to be used by POWER tooutput this report. Only used forLST queue.

Printer CC In Data 3 char UCC Specifies whether carriage controlappears as the first position of eachinput line.Can be '*', No, or ASA.'*' means use 'ccupload' driver dataoption.'No' if input does not containcarriage control.'ASA' if input contains ASAcarriage control.

DRIVER DATA



DRIVER DATA: jobname class origuser destuser altdel ccoption ccupload ________ ________ ________ ________ ________


jobname

This is a generic jobname that all reports must match to qualify for a downloadselection. This can be used to restrict access to specific jobs or reports. Refer to thesection “Download Selection Dialog” on page 97 for a description of a genericfield. Leave this field blank if you want access to all jobs and reports.

class

This is a list of up to 8 classes that all reports must match to qualify for adownload selection. This can be used to restrict access to specific jobs or reportsby class. Leave this field blank if you want access to all jobs and reports. Aspecification of ABCD for class would mean that only reports in classes A, B, C,and D would be accessible for downloads.

origuser

This field is used to restrict access to reports based on the originating user ID. Ifthis field is specified as '$USER', then only reports with an originating user IDmatching the PC users ID will qualify for a download selection. If any othervalue is specified here, it is assumed to be a generic userid that must match thereports origination user ID. Refer to the section “Download Selection Dialog” on



page 97 for a description of a generic field. Leave this field blank if you wantaccess to all jobs and reports.

destuser

This field is used to restrict access to reports based on the destination user ID. Ifthis field is specified as '$USER', then only reports with a destination user IDmatching the PC users ID will qualify for a download selection. If any othervalue is specified here, it is assumed to be a generic userid that must match thereports destination user ID. Refer to the section “Download Selection Dialog” onpage 97 for a description of a generic field. Leave this field blank if you wantaccess to all jobs and reports.

altdel

This field is used to indicate to BIM-PC/TRANSFER that reports are to be alteredor deleted from the POWER queue following a successful download. This optionsis ignored if the transfer is not completed. The following options can be specifiedin this field:

DELETE Delete the transferred report or job from the queue.

Alter the transferred report or job Class, Disposition and orPriority to the values specified for 'cdp'. Specify a blank for anyfield not to be changed. For example:

ALTERZL0 alter to CLASS=Z,DISP=L,PRI=0ALTERZ 0 alter to CLASS=Z,PRI=0ALTERZ alter to CLASS=Z

ALTERcdp

ALTER 0 alter to PRI=0

ccoption

This field is used to indicate how BIM-PC/TRANSFER is to handle carriagecontrol for downloaded reports. If this field is left blank, all carriage control willbe converted to CRLF's, NL's and FF's based on the reports FCB. The field can beoverridden by the PC for downloads. The following options can be specified inthis field:

CC Pass the actual carriage control byte from POWER in the firstposition of each line sent to the PC.

CCASA Convert machine carriage control to ASA, and pass them to the PCin the first position of each line.

CCDATA Ignore all carriage control in the report. Also ignore the FCB.

CCAFP Used to download reports that were created in a special format foradvanced function printers.



ccupload

This field is used to indicate how BIM-PC/TRANSFER is to handle carriagecontrol for uploaded reports. If this field is left blank, carriage control will bedetermined by standard ASCII CRLF's, NL's and FF's. If CCASA is specified inthis field, then it is assumed that the first position of each data line contains anASA carriage control character. This option can be overridden by the UploadDialog field "Printer CTL In Data".


Page 362 (BIMFTRDQ - QSAM) Driver Specifications

BIMFTRDQ - Sequential (QSAM) Dataset Driver (MVS Only)

This driver is used to upload data to and download data from MVS SequentialQSAM Datasets.

The datasets can have a RECFM of F, FB, VB or U, and must have an LRECL notgreater than 29900.

This driver uses the “Dataset Access Definitions” defined in the “UserDefinition” for access authorization to specific Datasets.








CRLF Default Y

TRANSLATE Default Y


Actual record length for downloads, 80 foruploads.


The following field will be presented on the PC in a dialog box when a downloadis requested for this driver. This field is used to specify which dataset(s) shouldbe presented in the PC File Transfer Window.


Dataset 44 char DSN Required. This is the generic nameof the dataset(s) desired. You mustspecify at least the high-levelqualifier:TEST.*TEST.FILE*

The following is not valid:TEST*

Download ScriptName



Driver Specifications (BIMFTRDQ - QSAM) Page 363


The following fields will be presented on the PC in a dialog box when a upload isrequested for this driver. These fields are used to specify the name and attributesof the dataset to be uploaded. The attributes are only used when uploading anew dataset.


Dataset 44 char DSN Required. This is the completename of the dataset. If the this isspecified as a generic value, aspecial list box will be generated onthe PC containing all matchingdatasets from the catalog. The PCuser can than select the specificdataset to be used. The genericname must include the high-levelqualifier.

GDG 8 char GDG If the Dataset is a GDG base, thisfield contains the relativegeneration.

SMS Mgmt Cl 8 char SMM This is the SMS Management Classfor a new dataset.

SMS Strg Cl 8 char SMS This is the SMS Storage Class for anew dataset.

SMS Data Cl 8 char SMD This is the SMS Data Class for anew dataset.

Recfm 2 char RFM This is the record format for a newdataset. This can be:VB, FB, F, U

Lrecl 5 num LRL This is the logical record length fora new dataset. This can be between4 and 29900.

Blksize 5 num BLK This is the block size for a newdataset. This can be between 8 and29900.

Space-Type 3 char SPT This field indicates the type ofspace allocation for a new dataset.This can be TRK or CYL.

Space-Pri 5 num SPP This field contains the primaryspace allocation for a new dataset.

Space-Sec 5 num SPS This field contains the secondaryspace allocation for a new dataset.

Volser 6 char VOL This field contains the Volumeserial number to be used for a newdataset.


Page 364 (BIMFTRDQ - QSAM) Driver Specifications

Unit 8 char UNT This field contains the unitdesignation for a new dataset.

GDG Model 44 char GDM This field contains the GDG modelto be used for a new generationdataset.

DRIVER DATA



DRIVER DATA: ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ %DRVD


%DRVD



Driver Specifications (BIMFTRDR - LIBR) Page 365

BIMFTRDR - VSE Library Access Using BIM-EDIT (VSE Only)

This driver is used to download members and upload members to a VSE Libraryusing the LIBR interface of BIM-EDIT. This driver can be used by BIM-EDITcustomers as an alternative to driver BIMFTRDL which uses a batch partition tointerface to LIBR.

Signon Requirements The USER ID and PASSWORD used on thePC must be defined to BIM-EDIT. Thisdriver will logon to BIM-EDIT prior toperforming the transfer.







CRLF Default OBJ, PHASE, E, and DUMP types default to'N', all others default to 'Y'.

TRANSLATE Default (same as CRLF default)


80




Library.Sublib 16 char LIB Required. This is the VSE libraryand sub-library to be searched forthe desired members.


This is the source type, OBJ, etc.Download ScriptName



Page 366 (BIMFTRDR - LIBR) Driver Specifications




Library.Sublib 16 char LIB Required. This is the VSE libraryand sub-library into which themember is to be loaded.


Type 8 char TYP Type of the member. This is thesource type, OBJ, etc. If omitted,the PC filename extension is used.

Data in PROC 1 char DAT This field is only used if the Typefield is PROC. It indicates whetherthe procedure contains data withinit. This field must be specified as Yor N, for yes/no. Default is 'N'. forno data in procedure.

Case 1 char CAS Case of member in LIBR:M Mixed (default)U Upper (member text will

be translated to upper case)

DRIVER DATA



DRIVER DATA: lu62 bimedit lu62unit lu62lmod lu62appl ________ ________ ________ ________ ________ ________ ________


lu62

Specify LU62 in this field if you want to use the LU 6.2 interface to BIM-EDIT.Leave this field blank if you want to use the XPCC interface. Refer to the BIM-EDIT System Reference Manual for more information on the LU 6.2 interface.


Driver Specifications (BIMFTRDR - LIBR) Page 367

bimedit

This field contains the BIM-EDIT system name. The default is BIMEDIT. If youhave more than one BIM-EDIT system, you can specify the name of the desiredsystem here.

lu62unit

This field is used for the LU 6.2 interface to BIM-EDIT. It contains the LogicalUnit name to be used for the connection to BIM-EDIT. The default is BIMAPPL.

lu62lmod

This field is used for the LU 6.2 interface to BIM-EDIT. It contains the Logmodename to be used for the connection to BIM-EDIT. The default is EDITLU62.

lu62appl

This field is used for the LU 6.2 interface to BIM-EDIT. It contains the APPLname to be used for the connection to BIM-EDIT. The default is BIMEDIT.


Page 368 (BIMFTRDT - CICS TD) Driver Specifications

BIMFTRDT - CICS Transient Data Upload Driver

This driver is used to upload records to a CICS Transient Data Queue.



Downloads Supported NO




EXIT Supported NO

CRLF Default Y

TRANSLATE Default Y


Maximum record length defined for thespecific Transient Data Queue if runningCICS/VSE 2.1 or above, or CICS/MVS 3.3 orabove, otherwise zero.


The following field will be presented on the PC in a dialog box when a upload isrequested for this driver.:


Transient DataQueue

4 char Q Name defined in CICS DCT.

DRIVER DATA



DRIVER DATA: truncate PADhh ________ ________ ________ ________ ________ ________ ________ ________ ________ ________


truncate

Specify TRUNCATE in this field if you want the driver to truncate any uploadedrecords that are larger than the maximum allowed for the specified Transient


Driver Specifications (BIMFTRDT - CICS TD) Page 369

Data Queue. If this option is omitted, message BIMFTRDT-3 will be generated ifa larger than allowed record is detected. This option is only supported inCICS/VSE 2.1 and above, or CICS/MVS 3.3 and above.

PADhh

'hh' is the hex value to be used as the pad character for any uploaded records thatare shorter than what is defined for a fixed-length Transient Data Queue. If thisoption is omitted, PAD40 is assumed, which will pad with blanks. Fixed lengthTransient Data Queues can only be detected in CICS/VSE 2.1 and above, orCICS/MVS 3.3 and above. Prior to those releases of CICS, all queues are assumedto be variable length.


Page 370 (BIMFTRDV - VSAM) Driver Specifications

BIMFTRDV - VSAM Dataset Driver (Using Profiles)

This driver is used to upload records to and download records from VSAMdatasets. These can be datasets that are defined to CICS via FCT entries, or byspecific VSAM Cluster Name. Refer to section "Cluster Name Transfer Feature"on page 205 for more information.

This driver uses VSAM Profile Definitions created by the FTRM transaction tocontrol the transfer. These are described in section " REF _Ref439135990 \hVSAM Profile Definition Screen" starting on page 204. If you want to performVSAM transfers via Cluster Name, and you don't want to define VSAM Profiles,then refer to section " REF _Ref439132863 \h BIMFTRDC - VSAM Cluster Driver"on page 315.

KSDS, RRDS and variable length or unblocked ESDS datasets can be uploaded ordownloaded. Uploads require the use of a formatting / selection exit unless:


• The data from the PC is separated into records with CRLFs.

Fixed-Blocked ESDS datasets are only supported if the host side of BIM-PC/TRANSFER is being executed in BIM-TMAN. CICS does not support accessto Fixed-Blocked ESDS datasets.

If you are uploading to a fixed length VSAM dataset, without an exit, and the PCrecords are separated with CRLFs, then all PC records must be the length definedfor the VSAM dataset unless the PAD and/or TRUNCATE Driver Data optionsare used.

For downloads to the PC, all records within a specified key range (specified inthe Profile) will be sent to the PC, unless an EXIT is utilized.

For uploads from the PC, existing records are read and updated by key, or newrecords are added by key. If you want the entire file replaced, refer to the EMPTYDriver Data option below.


Uploads Supported YES (may require an EXIT)


Upload NEW Supported NO at the file level, YES at the VSAM recordlevel. (See EMPTY Driver Data Option)

Upload REPLACE Supported YES (at the VSAM record level)

Upload APPEND Supported YES (See EMPTY Driver Data Option)


CRLF Default Y


Driver Specifications (BIMFTRDV - VSAM) Page 371

TRANSLATE Default Y



Remote Files in CICS

Access to remote files in CICS is supported for CICS/VSE releases 2.2 and above,and CICS/MVS releases 3.3 and above. You must define a PPT/RDO programentry for module BIMFTRSM in each CICS system that owns a file to be accessed.Since this is a MRO/ISC connection, transfer performance will be poor. Youshould avoid large transfers of remote files.


The following fields will be presented on the PC in a dialog box when adownload is requested for this driver. These fields are used to specify whichVSAM Profiles should be presented in the PC File Transfer Window. Fields thatare left blank will not be used for selection processing.


Profile Name 16 char PRO VSAM Profile Name. If left blank,all profiles will be selected. Thiscan also be specified as a genericvalue.

Description 40 char DSC Profile Description. This willnormally require a genericspecification.

Dataset 8 char DAT Used to qualify selection to VSAMprofiles for a specific VSAMdataset.







Download ScriptName

16 char SCP Specifies a File Conversion Scriptname to be used for the download.This name must match a scriptdefined to the Host. This overridesany script or exit specified in theVSAM profile.

Cluster Name 44 char DSN Specifies the VSAM Cluster Nameto be transferred. This can only bespecified for Profiles that contain aDATASET name beginning with'BIM$'.

Catalog Name 8 char CAT (VSE Only) Specifies the DLBLname of the catalog in which theCluster Name is cataloged. If leftblanks, the VSAM Master Catalogis assumed.

Refer to section "Cluster Name Transfer Feature" on page 205 for moreinformation about using Cluster Names.


The following fields will be presented on the PC in a dialog box when a upload isrequested for this driver. These fields are used to specify the name of the VSAMProfile to be used for the upload:


Profile Name 16 char PRO VSAM Profile Name. If this isspecified as a generic value, aspecial list box will be generated onthe PC containing all matchingprofiles. The PC user can thanselect the specific profile to be used


Driver Specifications (BIMFTRDV - VSAM) Page 373

Cluster Name 44 char DSN Specifies the VSAM Cluster Nameto be transferred. This can only bespecified for Profiles that contain aDATASET name beginning with'BIM$'.

Catalog Name 8 char CAT (VSE Only) Specifies the DLBLname of the catalog in which theCluster Name is cataloged. If leftblanks, the VSAM Master Catalogis assumed.

Refer to section "Cluster Name Transfer Feature" on page 205 for moreinformation about using Cluster Names.

DRIVER DATA



DRIVER DATA: open close truncate PADhh ________ ________ empty ________ ________ ________ ________ %DRVD


open

Specify OPEN in this field if you want the driver to open the CICS dataset priorto the transfer. If this option is omitted, the dataset must already be open to CICS.

close

Specify CLOSE in this field if you want the driver to close the CICS dataset afterthe transfer. If this option is omitted, the dataset will remain open.

truncate

Specify TRUNCATE in this field if you want the driver to truncate any uploadedrecords that are larger than the maximum allowed for the defined VSAM dataset.If this option is omitted, message BIMFTRDV-12 will be generated if a larger thanallowed record is detected.

PADhh

Specify PAD in this field if you want the driver to pad any uploaded records thatare shorter than what is defined for a fixed-length VSAM dataset. 'hh' is the hexvalue to be used as the pad character. 'PAD40' will pad the record with spaces. Ifthis option is omitted, message BIMFTRDV-12 will be generated if a shorter thanallowed record is detected.



empty

Specify EMPTY in this field if you want the driver to open reusable VSAM ESDSfiles (or VSAM-managed SAM for VSE) with the EMPTY option during uploadsthat specify the “REPLACE” option for REPLACE/NEW/APPEND. This optionis ignored if the OPEN Driver Data option is not specified, or if the uploadrequest specifies the “NEW” or “APPEND” option.

%DRVD



Driver Specifications (BIMFTRDX - Scripts) Page 375

BIMFTRDX - Script File Access

This driver is used to upload scripts to and download scripts from the BIM-PC/TRANSFER Host Control File.







EXIT Supported NO

CRLF Default Y

TRANSLATE Default Y


72


The following fields will be presented on the PC in a dialog box when adownload is requested for this driver. These fields are used to specify whichVSAM Scripts should be presented in the PC File Transfer Window. Fields thatare left blank will not be used for selection processing.


Script Name 16 char NAM VSAM Script name. If left blank, allscripts will be selected. This canalso be specified as a generic value.

Description 40 char DSC Script description. This willnormally require a genericspecification. See section“Download Selection Dialog” onpage 97 for a description of generic.


Page 376 (BIMFTRDX - Scripts) Driver Specifications


The following fields will be presented on the PC in a dialog box when a upload isrequested for this driver. These fields are used to specify the name description ofthe VSAM Script being uploaded:


Script Name 16 char NAM VSAM Script name. If this isspecified as a generic value, aspecial list box will be generated onthe PC containing all matchingscript names. The PC user can thanselect the specific script to be used

Description 40 char DSC Script description.

DRIVER DATA

This driver does not currently use any DRIVER DATA fields.


VSE Interactive Interface Page 377

VSE/SP Interactive InterfaceThe FTRT host CICS transaction, used by the PC transfer program, can beactivated from a VSE Interactive Interface selection panel, instead of the normalblank CICS screen, by performing the following steps:

1) Create an Application Profile for BIM-PC/TRANSFER using the followingexample.

The NAME of the application can be any value not already used in yourenvironment.

The ACTIVATE value must be the CICS Tran ID you have used for the BIM-PC/TRANSFER FTRT transaction.

The DATA value must be specified exactly as shown below.

IESADMAP ADD OR CHANGE APPLIATION PROFILE

NAME.......... BIMPCTFR Unique application name, 1-8 characters.

CODE.......... 1 1=START trans ID, 2=LINK to program, 3=ATTACH NON- CONVERSATIONAL trans ID with data, 4=ATTACH CONVERSATIONAL trans ID with data.

ACTIVATE...... FTRT Name to activate, a 1-8 character program name or a 1-4 character transaction ID.

CASE.......... 1 Terminal input passed to application in upper case only(CASE=1) or upper/lower case(CASE=2).

DATA.......... BIMPCTFRIES1 <== Optional input data to pass to application.

SHOW.......... 2 Show input data(SHOW=1) or do not show it(SHOW=2).

PF1=HELP 3=END 4=RETURN 5=UPDATE

2) Add the Application Profile for BIM-PC/TRANSFER to the desired SelectionPanel(s) as shown below.


Page 378 VSE Interactive Interface

IESADMSPA ADD OR CHANGE SELECTION PROFILE

To add a new offer, key into one of the blank lines with a number on it. To delete a selection, erase the sequence number. To change text or selection of an offer, key over the data you wish to alter. To resequence the offers, key new sequence numbers over the old ones.

SELECTION PANEL NAME.... BIMEPROG

SEQ NAME TYPE SELECTION TEXT

1 IESLIBXX 1 Program Development Library 2 BIMPCTFR 1 BIM-PC/TRANSFER (FTRT) 3 IESP$EXE 1 Create Application Jobstream 4 IESEPROB 2 Problem Handling 5 BIMEPOPS 2 Operations 6 BIMEFILE 2 File Management 7 IESNICCF 1 Command Mode (ICCF) 8 BIMECICA 2 CICS Supplied Transactions 9 BIMPDOC 1 System Console (PDOC)

PF1=HELP 3=END 4=RETURN 5=UPDATE


User Security Exits Page 379

User Security ExitsA User Security Exit can be written if you wish to control the transfer processbeyond the controls that are provided via the FTRM transaction.

BIM-PC/TRANSFER provides for the specification of a user written security exiton the SYSTEM DEFINTION screen and on the CATEGORY DEFINITIONscreen.

User written security exits are standard CICS Command-Level programs writtenin any language you wish. They must be defined to CICS just like any other CICSapplication program. BIM-PC/TRANSFER issues an EXEC CICS LINK to yourexit program passing a COMMAREA containing the “Security Exit InterfaceParameter Area”. A sample security exit is provided (BIMFTRSX.A) written inassembler.

If you are using BIM-TMAN instead of CICS, then your exit must be written inCommand-Level Assembler.

Security Exit Interface Parameter Area

The following parameter area is passed to the security exit as COMMAREA data:

01 FTSXAREA. 05 FTSXFUNC PIC X. 05 FTSXRC PIC X. 05 FTSXRNAO PIC X. 05 FILLER PIC X. 05 FTSXUSID PIC X(8). 05 FTSXPSWD PIC X(8). 05 FTSXDRVR PIC X(8). 05 FTSXCATN PIC X(8). 05 FTSXLIBQ PIC X(44). 05 FILLER PIC X(12). 05 FTSXENTL PIC S9(8) COMP. 05 FTSXENT PIC X(1024).


Page 380 User Security Exits

FTSXFUNC This field contains the function that is being requested by the PC.The security exit should examine the function along with therelated information available for the function request, anddetermine if the PC user is authorized. The following functionsare supported:

S Signon requestL Logoff requestU Upload requestD Download requestI Category inquiry1 Query first matching entryQ Query all matching entries

FTSXRC This field contains the response to the requested function asdetermined by the security exit. The following responses aresupported:

space Function is allowed as requested.M Function is allowed as modified by security exit.N Function is not allowed. Return standard message to PC.S Function is not allowed. Return message in field

FTSXENT for length specified in field FTSXENTL to PC.

FTSXRNAO This field contains the type of upload requested. The security exitcan change this value if FTSXRC=M is used:

R Replace existing member if present.N Add new member.A Append to end of existing member.

Provided for function: U

FTSXUSID This field contains the user id of the PC user. The security exit canchange this value if FTSXRC=M is used.

Provided for functions: All

FTSXPSWD This field contains the password of the PC user. The security exitcan change this value if FTSXRC=M is used. The password fieldis encrypted. A subroutine (BIMFTRPW) has been provided toallow the security exit to decrypt and encrypt passwords. Thissubroutine is defined at the end of this section.

Provided for functions: All

FTSXDRVR This field contains the name of the driver program that will beused to complete the function. The security exit can change thisvalue if FTSXRC=M is used.

Provided for functions: U, D, I, 1, Q

FTSXCATN This field contains the name of the category that was selected bythe PC for the current function. The security exit can change this


User Security Exits Page 381

value if FTSXRC=M is used.

Provided for functions: U, D, I, 1, Q

FTSXLIBQ This field contains the LIBQUE value for the current function.The contents of this field is based on the driver being used. Referto the LIBQUE field of the “Category Definition Screen” on page195 for the valid contents of this field. The security exit canchange this value if FTSXRC=M is used.

Provided for functions: U, D, 1, Q

FTSXENTL This field contains the length of the following field (FTSXENT).The security exit can change this value if FTSXRC=M is used or ifan error message is to be returned.


FTSXENT This field contains a directory entry for function (D) or a selectionentry for functions (D, 1, Q). Its length is provided in fieldFTSXENTL. The security exit can change this value if FTSXRC=Mis used or if an error message is to be returned.


The format of this field is based on the driver being used. Adirectory entry is the same format as displayed on the PC screen.The selection entry is the series of fields presented in theupload/query dialog boxes on the PC. Refer to the sample UserSecurity Exit (BIMFTRSX.A) for more information on this area.


Page 382 User Security Exits

Subroutine BIMFTRPW

This subroutine can be called by your security exit to encode and decodepasswords that are maintained and used by BIM-PC/TRANSFER.

The subroutine is called using a standard COBOL or BAL CALL statement:

CALL 'BIMFTRPW' USING FTPWAREA.

and is passed a 32 byte area of the following format:

01 FTPWAREA. 05 FTPWFUNC PIC X. 05 FTPWRC PIC X. 05 FTPWIC PIC X. 05 FILLER PIC X. 05 FTPWPSWD PIC X(8). 05 FILLER PIC X(20).

FTPWFUNC Function code:

E Encode the password in FTPWPSWDD Decode the password in FTPWPSWD

FTPWRC Return code:

space Function completed? Unknown functionC Invalid character in password (see FTPWIC)

FTPWIC This field will contain the invalid character that was found.

FTPWPSWD Password to be encoded or decoded. The returned value is alsoplaced in this field.


Format / Selection Exits Page 383

Format / Selection ExitsA Format / Selection Exit can and sometimes must be written if you wish totransfer data to and from VSAM datasets or the IBM Host Transfer File. You canalso use these exits for all downloads, and some uploads. These exits can be usedto perform the following functions:

• Reformat data between the PC and the Host.• Select which records/lines are to be included in a transfer.

BIM-PC/TRANSFER provides for the specification of these exits on theCATEGORY DEFINITION screen in field EXIT. Refer to the section “DriverSpecifications” starting on page 306. The section for each driver specifies whenthese exits are supported.

You must write one of these exits if you desire to perform any of the followingtransfers:

• Uploading data to the IBM Host Transfer File or a VSAM dataset that isvariable length, and not separated by CRLFs. For this type of transfer, theexit must determine the length of each input line/record, and perform anydata conversion.

• Uploading data to an RRDS VSAM dataset. For this type of transfer, the exitmust determine the length of each input line/record, the RRN of each record,and perform any data conversion.

These exits are standard CICS Command-Level programs written in anylanguage. They must be defined to CICS just like any other CICS applicationprogram. BIM-PC/TRANSFER issues an EXEC CICS LINK to your exit programpassing a COMMAREA containing the “Format/Selection Exit InterfaceParameter Area”. A sample exit is provided (BIMFTRFX.A) written in assembler.

If you are using BIM-TMAN instead of CICS, then your exit must be written inCommand-Level Assembler.


Page 384 Format / Selection Exits

Format/Selection Exit Interface Parameter Area

The following parameter area is passed to your exit as COMMAREA data:

01 FTFXAREA. 05 FTFXFUNC PIC X. 05 FTFXTYPE PIC X. 05 FTFXRC PIC X. 05 FTFXCOMP PIC X. 05 FTFXTERM PIC X(4). 05 FTFXTRAN PIC X(4). 05 FTFXTASK PIC S9(7) COMP-3. 05 FTFXUSID PIC X(8). 05 FTFXDRVR PIC X(8). 05 FTFXCATN PIC X(8). 05 FTFXLIBQ PIC X(44). 05 FTFXDATA-D$. 10 FTFXD$FN PIC X(8). 10 FTFXD$FT PIC X(8). 10 FTFXD$OW PIC X(8). 10 FTFXD$ST PIC X. 10 FILLER PIC X(39). 05 FTFXDATA-DV REDEFINES FTFXDATA-D$. 10 FTFXDVDD PIC X(8). 10 FTFXDVDS PIC X(44). 10 FTFXDVTY PIC X(2). 10 FTFXDVRI PIC S9(8) COMP. 10 FTFXDVFC PIC X. 10 FILLER PIC X(5). 05 FTFXDATA-DE REDEFINES FTFXDATA-D$. 10 FTFXDENM PIC X(16). 10 FTFXDETY PIC X(8). 05 FTFXLLEN PIC S9(8) COMP. 05 FTFXTRTO PIC X. 05 FTFXCRLF PIC X. 05 FILLER PIC X(14). 05 FTFXINPL PIC S9(8) COMP. 05 FTFXINPA PIC S9(8) COMP. 05 FTFXMAXL PIC S9(8) COMP. 05 FTFXMODL PIC S9(8) COMP. 05 FTFXMODA PIC S9(8) COMP. 05 FTFXWORK PIC X(256).



FTFXFUNC This field contains the function that is being requested by thetransfer driver:

O Open/initiate transferN Next Record/Line requestedX End of Transfer

FTFXTYPE This field contains the type of transfer being performed:

U Upload from PC to HostD Download from Host to PC

FTFXRC This field must be set by the exit to indicate to the transfer driverwhat action to be taken next:

space Open processing successfulKeep record/line as is

D Delete record/line from transferI Insert new record/line into transferM User modified record/lineX Cause driver to terminate transfer

FTFXCOMP This field contains the completion code when FTFXFUNC = 'X':

space successful completionA ATNI abend with PC connectionX Transfer canceled by PC userE Error detected by host software

FTFXTERM This field contains the current CICS terminal ID.

FTFXTRAN This field contains the current CICS transaction ID.

FTFXTASK This field contains the current CICS task number.

FTFXUSID This field contains the current PC user ID.

FTFXDRVR This field contains the name of the transfer driver being used.

FTFXCATN This field contains the category name from the categorydefinition.

FTFXLIBQ This field contains the LIBQUE value for the current transfer. Thecontents of this field is based on the driver being used. Refer tothe LIBQUE field of the “Category Definition Screen” on page195 for the valid contents of this field.

FTFXD$FN This field contains the file name if driver BIMFTRD$ is being


Page 386 Format / Selection Exits

used.

FTFXD$FT This field contains the file type if driver BIMFTRD$ is being used.

FTFXD$OW This field contains the file owners user id if driver BIMFTRD$ isbeing used.

FTFXD$ST This field contains the file status if driver BIMFTRD$ is beingused. '1' = private, '2' = public, '3' = shared.

FTFXDVDD This field contains the VSAM datasets CICS FCT name if driverBIMFTRDV is being used.

FTFXDVDS This field contains the VSAM datasets base cluster name if driverBIMFTRDV is being used and you are using CICS 1.7 or above.

FTFXDVTY This field contains the VSAM datasets type if driver BIMFTRDVis being used and you are using CICS 1.7 or above. This field willcontain KS, RR, or ES.

FTFXDVRI This field contains the RRN for RRDS datasets, or the RBA forESDS datasets if driver BIMFTRDV is being used. For uploads toRRDS or ESDS datasets, this field must be provided by the exitfor each record.

FTFXDVFC This field can be used during uploads to specify the type offunction to be used for the current record:

space Update record if is exists, add record if it doesn't existA Add recordD Delete record

FTFXDENM This field contains the member name if driver BIMFTRDE isbeing used.

FTFXDETY This field contains the member type if driver BIMFTRDE is beingused.

FTFXLLEN For uploads, the exit must set this field during function 'O' to thenumber of bytes of input required for the maximum length inputrecord from the PC. The transfer driver will ensure that thisnumber of bytes of data will be available at each call to the exitwith function 'N' until the end of input from the PC is reached.



FTFXTRTO This field contains the translate option that will be used by thetransfer driver. The exit can change this value.

Y Translate EBCDIC to ASCIIN Don't translate the data* Driver default (same as 'Y')

FTFXCRLF This field contains the CRLF option that will be used by thetransfer driver. The exit can change this value.

Y Records are separated by CRLF'sN Records are not separated by CRLF's* Driver default (same as 'Y')

FTFXINPL For downloads, and function 'N', this field contains the length ofthe current record. The address of the record is contained in fieldFTFXINPA.

For uploads this field contains the length of the input datapointed to by field FTFXINPA. If the input data can be uploadedwithout data conversion, the exit must examine the input data todetermine the record length, change this field to the actual recordlength, and return to the transfer driver with FTFXRC set tospace. If data conversion is required, the exit must format therecord in the area pointed to by field FTFXMODA, set the actualrecord length of the converted record in field FTFXMODL, set thelength of the input data used for the conversion in this field, andreturn to the transfer driver with FTFXRC set to 'M'.

FTFXINPA This field contains the address of the input data.

FTFXMAXL This field contains the length of the data area pointed to by fieldFTFXMODA.

FTFXMODL This field contains the length of the current modified/insertedrecord/line in the area pointed to by field FTFXMODA.

FTFXMODA This field contains the address of the area to be used to constructrecords/lines to be inserted or modified during the transfer. Thisdata in this field is used by the transfer driver when fieldFTFXRC is set to either 'M' or 'I'.

FTFXWORK This field can be redefined and used by the exit as a work areathat will be maintained by the transfer driver for the length of thetransfer. It is initialized to low-values at the start of the transfer.


Page 388 Default Translate Tables

Default Translate TablesBIM-PC/TRANSFER uses translate module BIMFTRTT for conversion betweenEBCDIC and ASCII.

BIMFTRTT is 512 bytes long, containing two 256 byte translate tables. The firsttable is used to convert EBCDIC to ASCII. The second table is used to convertASCII to EBCDIC.

EBCDIC To ASCII Translate Table

0 1 2 3 4 5 6 7 8 9 A B C D E F0- 000102030405060708090A0B0C0D0E0F1- 101112131415161718191A1B1C1D1E1F2- 202122232425262728292A2B2C2D2E2F3- 303132333435363738393A3B3C3D3E3F4- 204142434445464748499B2E3C282B7C5- 2651525354555657585921242A293BAA6- 2D2F62636465666768697C2C255F3E3F7- 707172737475767778603A2340273D228- 806162636465666768698A8B8C8D8E8F9- 906A6B6C6D6E6F7071729A9B9C9D9E9FA- A07E737475767778797AAAABAC5BAEAFB- B0B1B2B3B4B5B6B7B8B9BABBBC5DBEBFC- 7B414243444546474849CACBCCCDCECFD- 7D4A4B4C4D4E4F505152DADBDCDDDEDFE- 5CE1535455565758595AEAEBECEDEEEFF- 30313233343536373839FAFBFCFDFEFF

The following offsets in this translate table, and their translated character offsetsin the "ASCII To EBCDIC Translate Table" cannot be changed. The charactersthey represent are used internally by BIM-PC/TRANSFER:

x'0A' x'6E' x'C1'-x'C9'x'0D' x'7A'-x'7E' x'D1'-x'D9'x'4B'-x'4F' x'81'-x'89' x'E2'-x'E9'x'50' x'8B' x'F0'-x'F9'x'5A'-x'5E' x'91'-x'99'x'6B'-x'6C' x'A1'-x'A9'


Default Translate Tables Page 389

ASCII To EBCDIC Translate Table

0 1 2 3 4 5 6 7 8 9 A B C D E F0- 000102030405060708090A0B0C0D0E0F1- 101112131415161718191A1B1C1D1E1F2- 405A7F7B5B6C507D4D5D5C4E6B604B613- F0F1F2F3F4F5F6F7F8F97A5E4C7E6E6F4- 7CC1C2C3C4C5C6C7C8C9D1D2D3D4D5D65- D7D8D9E2E3E4E5E6E7E8E9ADE0BD5F6D6- 798182838485868788899192939495967- 979899A2A3A4A5A6A7A8A9C04FD0A17F8- 808182838485868788898A8B8C8D8E8F9- 909192939495969798999A4A9C9D9E9FA- A0A1A2A3A4A5A6A7A8A95FABACADAEAFB- B0B1B24FB4B5B6B7B8B9BABBBCBDBEBFC- C0C1C2C3C4C5C6C7C8C9CACBCCCDCECFD- D0D1D2D3D4D5D6D7D8D9DADBDCDDDEDFE- E0E1E2E3E4E5E6E7E8E9EAEBECEDEEEFF- F0F1F2F3F4F5F6F7F8F9FAFBFCFDFEFF


Page 390 Default Translate Tables


Page 391

MESSAGES


Page 392 Messages


Messages Page 393

BIMFCV Error MessagesBIMFCV produces several error messages when reading in the File ConversionScript.

Script Input Errors

Script Input Errors are detected while BIMFCV is loading in the File ConversionScript. Processing will be terminated if an error is detected.

Each message is preceded by the line number of the File Conversion Script wherethe error was found.

The errors are:

Record type omitted, assume variable

#RECORD type must be either 'V' for variable, or 'F' for fixed.

Type invalid, character assumed

On a field definition, the field type was unrecognizable. BIMFCV assumescharacter, type X, and continues processing.

Conversion invalid, 'NONE' assumed

BIMFCV did not recognize the type of field conversion on a field definition.It will continue processing with a conversion of 'N' for none.

IF condition invalid

BIMFCV did not recognize the type of comparison specified on a #IFstatement.

Unable to locate field

BIMFCV could not find the field specified in a #IF statement. Remember, thefield must be previously defined.

Occurs invalid, 1 assumed

BIMFCV could not determine the repeat or occurs value for a field or#GROUPBEG statement.

BEGINGROUP/#ENDGROUP imbalance

There must be a corresponding #GROUPEND for each #BEGINGROUPencountered in the File Definition Script.

Offset omitted

The offset was omitted from a #GROUPBEG statement.


Page 394 Messages

BIMFTR-7nn Error MessagesThese messages are generated by the PC program. They are documented in theon-line help of the PC program.


Messages Page 395

Messages From Host During Transfer

BIMFTRCM-1 Unknown function request xxxxxxxxThe PC has sent an unknown request 'xxxxxxxx'. Request technical assistancefor this problem.

BIMFTRCM-2 Category not found, xxxxxxxxThe PC has sent an unknown category name 'xxxxxxxx'. Request technicalassistance for this problem.

BIMFTRCM-3 Driver xxxxxxxx not availableThe host could not access the driver 'xxxxxxxx' . If you are running BIM-PC/TRANSFER in CICS, use CEMT to check the status of the driver.

BIMFTRCM-6 Security Exit xxxxxxx not availableThe host could not access the security exit 'xxxxxxxx' . If you are runningBIM-PC/TRANSFER in CICS, use CEMT to check the status of the exit.

BIMFTRCM-7 Requested function not allowed (SX)A security exit your site has provided has rejected the current transferrequest.

BIMFTRCM-9 Invalid Signon requestYour signon request has been rejected by a security exit your site hasprovided.

BIMFTRCM-10 Dataset xxxxxxxx not availableThe host could not access the dataset 'xxxxxxxx' . If you are running BIM-PC/TRANSFER in CICS, use CEMT to check the status of the dataset. It mustbe open and enabled.

BIMFTRCM-11 Dataset xxxxxxxx out of spaceThe dataset 'xxxxxxxx' is full. Contact the person responsible for BIM-PC/TRANSFER.

BIMFTRCM-12 Dataset xxxxxxxx access error nnnn, RCODE=nnnnnnnnnnnnThe dataset 'xxxxxxxx' could not be accessed because of error 'nnnn'. Theerror number is from the field EIBRESP, and is documented in the section“EIBRESP Codes” on page 455.


Page 396 Messages

BIMFTRCM-13 Requested function not allowed

(Type)

(Grp)

The current category cannot be used for the current transfer. If (Type) isindicated, then the category is restricted to either uploads or downloads, andyou have requested the other type. If (Grp) is indicated, then your securitydefinition on the host does not allow you to use the current category.

BIMFTRCM-14 Requested Libque not allowedThe current category definition on the host has restricted transfers to specificLibque values. You have specified a Libque that is not allowed. The Libquevalue is the first field in each category selection dialog box presented on thePC.

BIMFTRCM-15 Translate table xxxxxxxx not availableThe host could not access the translate table 'xxxxxxxx' . If you are runningBIM-PC/TRANSFER in CICS, use CEMT to check the status of the module.

BIMFTRCM-16 UserID not definedThe entered UserID has not been defined to the host using the FTRMtransaction. Check that you entered the proper value.

BIMFTRCM-17 Invalid passwordThe entered password is not the same as the password defined to the host forthe entered UserID. Check that you entered the proper value.

BIMFTRCM-18 PC release xxxx not supported by yyyyThe release of the PC program you are using 'xxxx' is not supported by therelease of the host software 'yyyy;' you are using. Upgrade the PC software tothe release 'yyyy'.

BIMFTRCM-19 Module xxxxxxxx not availableThe host could not access the program 'xxxxxxxx' . If you are running BIM-PC/TRANSFER in CICS, use CEMT to check the status of the program.

BIMFTRCM-20 Upload

REPLACE

NEWAPPEND

option not allowed for this category

The Category Definition on the host has been defined with this upload optionas being disallowed.

BIMFTRCM-21 Log File Access error,xx,RRN=nnnnnnnn,RESP=nnnn,RCODE=nnnnnnnnnnnAn error occurred attempting to access the Host Activity Log. RESP is fromfield EIBRESP, and is documented in the section “EIBRESP Codes” on page455. Request technical assistance for this error.


Messages Page 397

BIMFTRCM-22 HOSTAFT support module nnnnnnnn not availableThe HOSTAFT control module (nnnnnnnn) must be defined to CICS as aprogram, and must be ENABLED. Check the status with CEMT and correct.

BIMFTRCM-23 Access Security Group xxxxxxxx not foundThe Category Definition you are using has been defined with an AccessSecurity Group, but no definition by that name can be found. The CategoryDefinition cannot be used until either the security definition is added, or thename removed from the category.

BIMFTRCM-24 START Command failed,Tran=xxxx, Term=xxxx, Resp=nnnn, Resp2=nnnnThe #START Command has been rejected by the host. The most commonreasons will be Resp=0028 which means unkown or unavailable tran id, andRESP=0011 which means unknown or unavailable terminal id. Refer tosection “EIBRESP Codes” on page 455 for other RESP values.

BIMFTRCM-25 START Command failed,Netname xxxxxxxx not found, Resp=nnnn, Resp2=nnnnThe #START Command has been rejected by the host. The most commonreason will be RESP=0011 which means unknown netname. Refer to section“EIBRESP Codes” on page 455 for other RESP values.

BIMFTRCM-26 Default User ID not DefinedThis message is generated when a PC user logs onto BIM-PC/TRANSFERwith a blank user id and the host has been defined with a “Default UserDefinition”, but the default user id has been deleted. Use the FTRMtransaction to update the ‘System Definition Screen” with the proper“Default User Definition”.

BIMFTRCM-9998 WARNING - PRODUCT AUTHORIZATION EXPIRES IN 30 DAYS OR LESSThis message is displayed if the copy of BIM-PC/TRANSFER you are usingis about to expire. Contact your BIM product sales representative for a newExpiration Password.

BIMFTRCM-9999 PRODUCT AUTHORIZATION HAS EXPIREDBIM-PC/TRANSFER is protected with an Expiration Password. Thismessage is displayed if that Password has expired. Contact your BIMproduct sales representative for a new Expiration Password.

BIMFTRD$-1 IND$ module xxxxxxxx not availableThe host could not access the module 'xxxxxxxx' . If you are running BIM-PC/TRANSFER in CICS, use CEMT to check the status of the module.

BIMFTRD$-2 IND$ filename xxxxxxxx not foundThe requested filename 'xxxxxxx' was not found in the IND$ dataset.


Page 398 Messages

BIMFTRD$-3 Undefined IND$ User ID xxxxxxxxThe specified User ID 'xxxxxxx' has not been defined to IND$.

BIMFTRD$-4 Not signed on to IUIYou must be signed on to the IBM Interactive User Interface beforeattempting transfers using the IND$ interface.

BIMFTRD$-5 IND$ interface error xxxxRequest BIM Technical Support for this message.

BIMFTRD$-6 IND$ filename xxxxxxxx already existsThe requested filename 'xxxxxxx' was found in the IND$ dataset and you didnot specify 'replace' for the upload.

BIMFTRD$-10 Dataset xxxxxxxx not availableThe host could not access the dataset 'xxxxxxxx' . If you are running BIM-PC/TRANSFER in CICS, use CEMT to check the status of the dataset. It mustbe open and enabled.

BIMFTRD$-12 Dataset xxxxxxxx access error nnnnThe dataset 'xxxxxxxx' could not be accessed because of error 'nnnn'. Theerror number is from the field EIBRESP, and is documented in the section“EIBRESP Codes” on page 455.

BIMFTRD$-13 Module xxxxxxx not availableThe host could not access the Script Processing Module 'xxxxxxxx' . If you arerunning BIM-PC/TRANSFER in CICS, use CEMT to check the status of themodule.

BIMFTRD$-15 Exit xxxxxxx not availableThe host could not access the Formatting/Selection exit 'xxxxxxxx' . If you arerunning BIM-PC/TRANSFER in CICS, use CEMT to check the status of theexit.

BIMFTRD$-16 IND$ not supported in BIM-TMANThe host side of BIM-PC/TRANSFER must be running in CICS to use theIND$ interface.

BIMFTRD$-17 IND$ not supported in APPCYou must be using an LU2/3270 connection for the IND$ interface. The IBMIND$ interface (INWMAPI) requires that you first log on to the InteractiveInterface on the host, which requires a 3270 session.

BIMFTRD$-18 IND$ TWA size of at least 256 required on transaction FTRTThe IBM IND$ interface (INWMAPI) requires a TWA size of 256 for itsprocessing.


Messages Page 399

BIMFTRD$-99 Host Abend-xxxx detectedThe host application abended. Request technical assistance for this error.

BIMFTRDB-1 Entry not found: lib.sublib.member.typeThe requested VSE Library member could not be found.

BIMFTRDB-2 Sublibrary (sublib) does not existThe requested VSE sublib could not be found.

BIMFTRDB-3 Library (library) does not existThe requested VSE library could not be found.

BIMFTRDB-4 LIBRM Error Response, RC=nnn, Reason=xxxxxxxxFunc: xxxxxxxx, For: lib.sublib.member.typeDesc: xxxxxxxx:Msg: libr error messageThe LIBRM interface has returned an unexpected response. If you are unableto determine the cause from the various fields in this message, then requestBIM technical assistance for this message. Have the entire message availablefor support.

BIMFTRDB-5 Library (library) out of spaceThe VSE Library (library) is full.

BIMFTRDB-6 Invalid Lib.Slib: library.sublibOnly Slib can be genericGeneric library names are not supported.

BIMFTRDB-7 Access Not Authorized for: lib.sublib.member.typeThe requested transfer has been rejected because of an Access SecurityDefinition that has been specified for the category you are using.

BIMFTRDB-8 New specified, but member already exists,lib.sublib.member.typeAn upload with the 'New' option has been specified, but the member.typealready exists in the library.sublib.

BIMFTRDB-9 Invalid Lib.Slib: library.sublibMust contain a periodThe VSE Library field must contain a 1-8 byte library name, followed by aperiod, and the requested sublibrary name.

BIMFTRDB-10 Record length of nnn exceeds max of mmmThe PC file contains a record that is to long. Specify the 'Truncate LongRecords' option to avoid this error.


Page 400 Messages

BIMFTRDB-11 Invalid character (char) in: nameValid characters are: A-Z 0-9 @ $ #Only the specified characters are suppored in VSE Library and membernames.

BIMFTRDB-12 Uploads to MSHP controlled members not allowedTo allow uploads to these members, you need to define a Category Definitionfor this driver with the 'mshp' Driver Data option.

BIMFTRDB-90 Subtask has terminated/abendedLast Func: xxxxxxxx, For: xxxxxxxx, RC=nnn, Reason=xxxxxxxxxx,bufl=nnn, usedl=nnn, reml=nnn, curl=nnn,'Desc=xxxxxxxx'The subtask processing the current VSE Library member has terminatedunexpectedly. Check your VSE system console for messages related to theabend. Request BIM technical assistance for this message. Have the entiremessage available for support.

BIMFTRDB-91 Zero Length recordLast Func: xxxxxxxx, For: xxxxxxxx, RC=nnn, Reason=xxxxxxxxxx,bufl=nnn, usedl=nnn, reml=nnn, curl=nnn,'Desc=xxxxxxxx'Internal processing error. Request BIM technical assistance for this message.Have the entire message available for support.

BIMFTRDB-92 Zero Length returnedLast Func: xxxxxxxx, For: xxxxxxxx, RC=nnn, Reason=xxxxxxxxxx,bufl=nnn, usedl=nnn, reml=nnn, curl=nnn,'Desc=xxxxxxxx'Internal processing error. Request BIM technical assistance for this message.Have the entire message available for support.

BIMFTRDB-99 Host Abend-xxxx detectedThe host application abended. Request technical assistance for this error.

BIMFTRDC-1 Cluster not foundvsam.cluster.nameReason: (catalog error description)The requested VSAM cluster could not be found in the requested VSAMcatalog.

BIMFTRDC-2 This driver requires CICS 1.7 or aboveThis driver uses CICS functions not available prior to CICS 1.7. You will needto runt the host under BIM-TMAN.


Messages Page 401

BIMFTRDC-3 (error text),RC=fdbk/reasonvsam.cluster.nameThis message is generated if an error occurs while attempting to extractinformation about a VSAM cluster from your VSAM catalog. (error text) willcontain a description of the type of access error:DD/DLBL NOT FOUNDCAT=xxxxxxx NOT FOUNDDATASET NOT FOUND IN CATALOGERROR OBTAINING CATALOG ACBCATLG ERROR - xxxxxxxxxxxxxxx

The RC= is from the VSAM catalog access routine. You may need to requesttechnical assistance for this error.

BIMFTRDC-4 Wrong Length Record, Max=nnnnn, Cur=nnnnnCluster: vsam.cluster.nameCurrent line is nnnnn, Data begins with:(data from input, translated to printable characters)This message is generated if, during an upload to the host, a data line isdetected with a length greater than the maximum allowed for the VSAMcluster. This message can be avoided by use of the TRUNCATE Driver Dataoption for driver BIMFTRDC. See page 319 for more information.

BIMFTRDC-5 Replace not authorized for this categoryThe PC user has requested an upload with the REPLACE option, but theEMPTY Driver Data option has not been specified. See 319 for moreinformation.

BIMFTRDC-6 Replace not allowed on this datasetCluster: vsam.cluster.nameThe PC user has requested an upload with the REPLACE option. REPLACEis only supported for ESDS datasets that have been defined as resusable. See"empty" on page 321 for more information.

BIMFTRDC-7 DLBL for Catalog ccccccc not foundA VSE Catalog DLBL name has been specified, but no DLBL of that name canbe accessed by the CICS or BIM-TMAN partition.

BIMFTRDC-9 Dataset ddname not supportedCluster: vsam.cluster.nameOnly VSAM datasets can be accessed using this driver.

BIMFTRDC-10 Dataset ddname not availableCluster: vsam.cluster.nameThe dataset could not be opened in CICS, or the FCT entry for "ddname" hasbeen marked disabled.

BIMFTRDC-11 Dataset ddname out of spaceCluster: vsam.cluster.nameThe dataset is full.


Page 402 Messages

BIMFTRDC-12 Dataset xxxxxxxx ffff access error eeee (text)Resp2=nnnn, Rcode=xxxxxxxxxxxx, Recl=lllllCluster: vsam.cluster.nameCurrent line is nnnnn, Data begins with:(data from input, translated to printable charactersThe dataset 'xxxxxxxx' could not be accessed for function 'ffff' because oferror 'eeee'. The error number is from the field EIBRESP, and is documentedin the section “EIBRESP Codes” on page 455. Most error numbers will bedisplayed in text form as (text). ‘lllll’ is the current record length. Resp2 andRcode will further define some types of errors. These are documented inCICS manuals for EIBRESP2 and EIBRCODE.If this error occurs during an upload, and it reports a LENGERR, and you areuploading to a fixed length VSAM dataset, then the most likely cause is theabsence of the "truncate" and "PADhh" Driver Data options on your VSAMCategory Definition. Refer to page 319 for more information.

BIMFTRDC-16 VSAM Allocation error,(allocation error text)An error has occurred while attempting to allocate the VSAM Cluster. Referto the section “Allocation / Deallocation Errors” on page 452 for adescription of the allocation error text.

BIMFTRDC-18 Dataset ddname currently in useCluster: vsam.cluster.nameAll of the FCT entries for BIM$UPn or BIM$DNn are in use for othertransfers. Try again later.

BIMFTRDC-22 VSAM De-allocation error,(de-allocation error text)An error has occurred while attempting to de-allocate the VSAM Cluster.Refer to the section “Allocation / Deallocation Errors” on page 452 for adescription of the de-allocation error text.

BIMFTRDC-30 Upload New not supported by this CategoryThe Upload New option is only supported in VSE with Categories definedwith the IDCAMS Driver Data Option. Refer to the section on driverBIMFTRDC starting on page 315 for more information about the IDCAMSoption.

BIMFTRDC-31 Upload New requires IDCAMS Delete/DefineThe Upload New option requires the specification of an IDCAMSDelete/Define script. Refer to the section on driver BIMFTRDC starting onpage 315 for more information about IDCAMS processing.

BIMFTRDC-32 IDCAMS Delete/Define not supported by this CategoryRefer to the section on driver BIMFTRDC starting on page 315 for moreinformation about the IDCAMS Driver Data option.


Messages Page 403

BIMFTRDC-33 Upload New specified, but Cluster: clustername already existsYou have requested an upload to a new VSAM cluster, but the specifiedcluster already exists. Either choose another name for your cluster, or use theupload replace option.

BIMFTRDC-34 Link to module BIMFTR98 failed, Resp=nnnnnThe link to the IDCAMS processing module, BIMFTR98 failed. The Respnumber is from the field EIBRESP, and is documented in the section“EIBRESP Codes” on page 455. Make sure the module is defined to CICS,and is in an enabled state.

BIMFTRDC-99 Host Abend-xxxx detectedThe host application abended. Request technical assistance for this error.

BIMFTRDD-1 Entry not foundThe requested PDS member could not be found.

BIMFTRDD-2 PDS could not be openedCheck for other error messages in the output message log that may indicatethe reason for the failure.

BIMFTRDD-3 SYNAD error occurred on input(synad error text)An error occurred during the processing of an input PDS. The second line ofthe message describes the specific type of error.

BIMFTRDD-4 PDS RECFM must be F, FB, or VBYou have attempted to access a PDS with an unknown or unsupportedrecord format.

BIMFTRDD-5 SYNAD error occurred on output(synad error text)An error occurred during the processing of an output PDS. The second lineof the message describes the specific type of error.

BIMFTRDD-6 PDS member xxxxxxxx already in PDSYou have attempted to upload a member with the 'new' option that alreadyexists in the PDS.

BIMFTRDD-7 PDS allocation error,(allocation error text)An error has occurred while attempting to allocate the PDS. Refer to thesection “Allocation / Deallocation Errors” on page 452 for a description ofthe allocation error text.


Page 404 Messages

BIMFTRDD-8 PDS de-allocation error,(de-allocation error text)An error has occurred while attempting to de-allocate the PDS. Refer to thesection “Allocation / Deallocation Errors” on page 452 for a description ofthe de-allocation error text.

BIMFTRDD-9 Abend xxx-xx during PDS InputAn I/O abend error has occurred while reading from the PDS. Refer to theMVS System Codes manual for a description of xxx-xx.

BIMFTRDD-10 Abend xxx-xx during PDS OutputAn I/O abend error has occurred while writing to the PDS. Refer to the MVSSystem Codes manual for a description of xxx-xx. The most likely error is anout-of-space condition.

BIMFTRDD-11 PDS Directory is FullThere is no space available in the directory to add this new member to thePDS. You will need to add more directory space to the PDS, or deleteunneeded members to make space available.

BIMFTRDD-12 PDS STOW error, RC=xxAn error occurred executing the STOW macro. The following values can bereturned for RC:

04 Directory already contains member08 Member not found0C Out of space in directory10 I/O error14 DCB not open for output18 Out of GETMAIN storage

BIMFTRDD-16 PDS BLDL error, RC=xxxxAn error occurred executing the BLDL macro. The following values can bereturned for RC:

0400 Entry not found0800 I/O error0804 Out of GETMAIN storage0808 Invalid DEB

BIMFTRDD-17 Requested Dataset is not a PDSThis driver can only process Partitioned Datasets. These are datasets with aDSORG=PO.

BIMFTRDD-18 Input line exceeds max for VB PDSYour PC file contains a line that is to long for this PDS.

BIMFTRDD-21 Lrecl exceeds maximum for driverThis PDS has a lrecl that is to large to be processed by this driver. Themaximum allowed is 29,900.


Messages Page 405

BIMFTRDD-99 Host Abend-xxxx detectedThe host application abended. Request technical assistance for this error.

BIMFTRDE-1 Entry not foundThe requested BIM-EDIT member could not be found.

BIMFTRDE-2 (message text from BIM-EDIT)(last command line given to BIM-EDIT)The requested transfer failed because of an error condition detected in BIM-EDIT. The second line of the message shows the BIM-EDIT command thatfailed.

BIMFTRDE-3 Member xxxxxxxxxxxxxxxx already checked outto library: xxxxxxxxxxxxxxxxThe requested transfer with checkout has failed because the BIM-EDITmember you have requested has already been checked out to anothercheckout library.

BIMFTRDE-4 Member xxxxxxxxxxxxxxxx already checked outfrom library: xxxxxxxxxxxxxxxxThe requested transfer with checkout has failed because the BIM-EDITmember you have requested has already been checked out from anothercheckout library.

BIMFTRDE-5 Member xxxxxxxxxxxxxxxx not checked outto library: xxxxxxxxxxxxxxxxThe requested transfer with checkout has failed because the BIM-EDITmember you have requested has already been checked out, but not to thecheckout library defined in the Category Definition.

BIMFTRDE-6 Access Not AuthorizedThe requested transfer has been rejected because of an Access SecurityDefinition that has been specified for the category you are using.

BIMFTRDE-99 Host Abend-xxxx detectedThe host application abended. Request technical assistance for this error.

BIMFTRDF-1 Dataset not foundThe requested SAM dataset could not be found.

BIMFTRDF-2 SAM Profile xxxxxxxxxxxxxxxx not foundThe requested SAM Profile could not be found.

BIMFTRDF-3 Subtask has terminated/abendedThe subtask processing the current dataset has terminated unexpectedly.Check your VSE system console for messages related to the abend.


Page 406 Messages

BIMFTRDF-4 Wrong Length Record, Max=nnnnn, Cur=nnnnnDataset: datasetnameCurrentLine is nnnnn, Data Begins with:(data from current line)A record from the PC contains an invalid length record. The Truncate andPad options may be used to prevent this message.

BIMFTRDF-5 Dataset out of spaceDataset: datasetnameCurrentLine is nnnnn, Data Begins with:(data from current line)No more extents are available for this dataset. You will need to allocate morespace.

BIMFTRDF-7 Downloads not allowed for Profile xxxxxxxxxxxxxxxxThis SAM Profile has been defined for uploads only.

BIMFTRDF-8 Access to Profile xxxxxxxx is not allowedThis SAM Profile has been secured with a SECGRP. You have not been givenaccess to the SECGRP via your host user definition.

BIMFTRDF-9 Uploads not allowed for Profile xxxxxxxxxxxxxxxxThis SAM Profile has been defined for downloads only.

BIMFTRDF-10 Dataset xxxxxxxx not availableThe host could not access the dataset 'xxxxxxxx' . If you are running BIM-PC/TRANSFER in CICS, use CEMT to check the status of the dataset. It mustbe open and enabled.

BIMFTRDF-11 Dataset xxxxxxxx out of spaceThe dataset 'xxxxxxxx' is full. Contact the person responsible for BIM-PC/TRANSFER.

BIMFTRDF-12 Dataset xxxxxxxx access error nnnnThe dataset 'xxxxxxxx' could not be accessed because of error 'nnnn'. Theerror number is from the field EIBRESP, and is documented in the section“EIBRESP Codes” on page 455.

BIMFTRDF-13 BIM-EPIC interface: xxxxxxxx is not availableThe BIM-EPIC interface module could not be accessed, or has not beendefined to CICS. Refer to the Installation section for more information.

BIMFTRDF-14 BIM-EPIC interface error:(description of error)Key: epickeyThe BIM-EPIC interface has reported and unexpected error. Contact BIMTechnical Support.


Messages Page 407

BIMFTRDF-15 Dataset attributes not known to BIM-EPICUse Category Option Button to specify valuesDataset: datasetnameYou will need to specify Record Format, Record size, and Block size for thisdataset.

BIMFTRDF-16 Invalid Recsize and Blocksize combinationRecfm=x, Recsize=nnnnn, Blocksize=bbbbbUse Category Option Button to specify valuesDataset: datasetnameThe combination you specified for Record Format, Record size, and Blocksize is not valid. Typically this error will occur for a fixed length file whenthe block size is not a multiple of the record size.

BIMFTRDF-17 Invalid Varblk LLBB field in block nnnnnLLBB=xxxxxxxx, should be: xxxxxxxxDataset: datasetnameYou have specified that the current dataset contains variable length records,but it is not in a valid LLBB format. Check to determine what the properrecord format is.

BIMFTRDF-18 Invalid Recsize and Blocksize combinationRecfm=x, Recsize=nnnnn, Blocksize=bbbbbDataset: datasetnameThe combination you specified for Record Format, Record size, and Blocksize is not valid. Typically this error will occur for a fixed length file whenthe block size is not a multiple of the record size.

BIMFTRDF-19 Dataset not defined to BIM-EPIC catalogDataset: datasetnameThe PC user has attempted to upload to a dataset name that is not defined toBIM-EPIC, and either Start Track 1 datasets are not supported, or the STrack1Pool Name and Extend Size fields were not specified.

BIMFTRDF-20 Dataset cannot be DownloadedDataset: datasetnameReason: reasontextThis dataset cannot be downloaded at this time because of a conditionspecified in the BIM-EPIC catalog (reasontext) Resolve the condition andattempt the download again.

BIMFTRDF-21 Allocation error,(allocation error text)An error has occurred while attempting to allocate the dataset. Refer to thesection “Allocation / Deallocation Errors” on page 452 for a description ofthe allocation error text.


Page 408 Messages

BIMFTRDF-22 De-allocation error,(de-allocation error text)An error has occurred while attempting to de-allocate the dataset. Refer tothe section “Allocation / Deallocation Errors” on page 452 for a descriptionof the de-allocation error text.

BIMFTRDF-23 BIM-EPIC Service Module (xxxxxxxx) error:Error: (text of error)The BIM-EPIC Service Module has reported an unexpected error. ContactBIM Technical Support.

BIMFTRDF-24 Pool Name pppppp Not Defined to BIM-EPICThe PC user has requested a Start Track 1 dataset upload, but the specifiedPool Name has not been defined to BIM-EPIC.

BIMFTRDF-25 I/O Error Detected in block/record nnnnnDataset: datasetnameCCB: xxxxxxxxxxxxxxxxCCWs 1-2: xxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxCCWs 3-4: xxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxCurrentLine is nnnnn, Data Begins with:(data from current line)An unexpected error occurred processing this dataset. If this is a SAMdataset, verify that the proper DLBL and EXTENTs have been provided.

BIMFTRDF-26 Delete and/or Update option not authorizedThe PC user has requested an EPIC dataset be deleted, or the last accessedjob name be changed, but the Driver Data options authorizing these featureshave not been set.

BIMFTRDF-27 Start Track 1 datasets not allowedThe PC user has requested an upload to an EPIC Start Track 1, but the DriverData option authorizing this feature has not been set, or the support is notactive in BIM-EPIC.

BIMFTRDF-28 Invalid data block in Fixblk input fileBlock=nnnnn, Recsize=nnnnn, Current Blocksize=bbbbbDataset: datasetnameThe dataset being downloaded has a block that is not a valid length.

BIMFTRDF-29 Extent #n is not assigned to Volser: vvvvvvFor DLBL: ddddddd, Dataset: datasetnameGetvce RC=rr, Volser=vvvvvv Flag=ff, Lno=xxxxThe dataset could not be accessed because the volser for one of the extentswas not assigned to the properly. The last line contains information from theGETVCE macro call that was used to validate the assignment.RC is the GETVCE return code:.

8 volume is not mounted or logical unit is not assigned.12 logical unit is assigned IGNORE.


Messages Page 409

16 device is not operational.20 invalid parmlist.28 device is not ready.

BIMFTRDI-1 Entry not foundThe requested ICCF member could not be found.

BIMFTRDI-2 /INCLUDE member xxxxxxxx not foundThe ICCF member being transferred contains a /INCLUDE member thatcould not be located.

BIMFTRDI-3 Nested /INCLUDE stack full/INCLUDEs can be nested up to 24 deep.

BIMFTRDI-4 Member being edited, cannot downloadThe requested member is currently being edited by an ICCF user. Try requestagain later.

BIMFTRDI-5 Decompression error type xRequest BIM Technical Support for this message.

BIMFTRDI-6 Access Not AuthorizedThe requested transfer has been rejected because of an Access SecurityDefinition that has been specified for the category you are using.

BIMFTRDI-7 Internal logic errorRequest BIM Technical Support for this message.

BIMFTRDI-8 VSE/ICCF library format errorRequest BIM Technical Support for this message.

BIMFTRDI-9 More than 256 extentsBIM-PC/TRANSFER cannot process an ICCF Library that contains morethan 256 extents.

BIMFTRDI-10 DLBL not found for 'xxxxxxxx'BIM-PC/TRANSFER could not find a DLBL for your ICCF Library.

BIMFTRDI-11 Only type 1 extents supportedBIM-PC/TRANSFER can only process an ICCF Library that contains “Type1” extents.

BIMFTRDI-12 Unsupported DTF device code x'xx'Request BIM Technical Support for this message.

BIMFTRDI-16 I/O error CSW=x'xxxx'Request BIM Technical Support for this message.


Page 410 Messages

BIMFTRDI-17 Upload not supported to ICCF libraryBIM-PC/TRANSFER cannot support uploads to ICCF because of the lack ofan IBM application interface to that library structure.

BIMFTRDI-18 GETVCE failure x'xx'Request BIM Technical Support for this message.

BIMFTRDI-99 Host Abend-xxxx detectedThe host application abended. Request technical assistance for this error.

BIMFTRDJ-1 Entry not foundThe requested JES report could not be found.

BIMFTRDJ-3 Required module xxxxxxxx not availableRefer to the Installation section for the required CICS table entries.

BIMFTRDJ-4 JES OPEN Failure, RC=xxxxHave the complete message text available when requesting technicalassistance for this problem.

BIMFTRDJ-5 Invalid SVC override - xxxxxxThe SVC driver data option must be the letters 'SVC' followed by a 3-digitSVC number (decimal).

BIMFTRDJ-6 Access Not AuthorizedThe requested transfer has been rejected because of an Access SecurityDefinition that has been specified for the category you are using.

BIMFTRDJ-7 INTRDR allocation error,(allocation error text)An error has occurred while attempting to allocate the internal reader. Referto the section “Allocation / Deallocation Errors” on page 452 for adescription of the allocation error text.

BIMFTRDJ-8 INTRDR could not be openedCheck for other error messages in the output message log that may indicatethe reason for the failure.

BIMFTRDJ-9 SYNAD error occurred during output(synad error text)An error occurred during the processing of the internal error. The second lineof the message describes the specific type of error.

BIMFTRDJ-10 Abend xxx-xx during INTRDR OutputAn I/O abend error has occurred while writing to the internal reader. Referto the MVS System Codes manual for a description of xxx-xx.


Messages Page 411

BIMFTRDJ-16 JES Access Error, Func=xxx, RC=xxxxHave the complete message text available when requesting technicalassistance for this problem.

BIMFTRDJ-99 Host Abend-xxxx detectedThe host application abended. Request technical assistance for this error.

BIMFTRDL-1 Entry not foundThe requested VSE Library member could not be found.

BIMFTRDL-5 Invalid Lib.Slib, Only Slib can be genericThe requested query specified a generic "Lib". This is not supported. The full"Lib" must be provided because it is required to access a correspondingDLBL.

BIMFTRDL-6 Access Not AuthorizedThe requested transfer has been rejected because of an Access SecurityDefinition that has been specified for the category you are using.

BIMFTRDL-99 Host Abend-xxxx detectedThe host application abended. Request technical assistance for this error.

BIMFTRDL-22nn (common messages)These messages are described in the common message section “BIMFTRxx-nnnn Messages” starting on page 443.

BIMFTRDL-25nn (common messages)These messages are described in the common message section “BIMFTRxx-nnnn Messages” starting on page 443.

BIMFTRDM-1 TS Queue: qqqqqqqq not foundEIBRESP=nnn(text), SYSID=ssssThe requested Temporary Storage Queue (qqqqqqqq) could not be found forCICS SYSID=ssss. The CICS response code is provided (EIBRESP).

BIMFTRDM-2 TS Queue: qqqqqqqq already existsSYSID=ssssThe requested Temporary Storage Queue (qqqqqqqq) already exists for CICSSYSID=ssss. This message is returned if an upload request has been made fora NEW Temporary Storage Queue that already exists. This error will notoccur for APPEND or REPLACE.

BIMFTRDM-3 TS Queue: qqqqqqqq write errorEIBRESP=nnn(text), SYSID=ssssCICS reported an error (EIBRESP) when attempting to write a line to theTemporary Storage Queue (qqqqqqqq).


Page 412 Messages

BIMFTRDM-4 Line length of xxxxx exceeds max supported of mmmmmThe member you are uploading or the Temporary Storage Queue you aredownloading contains a line that is longer than the maximum supported bythis driver. The maximum is 'mmmmm', the invalid line has a length of'xxxxx'.

BIMFTRDM-5 TS Queue: qqqqqqqq read errorItem=iiiii, EIBRESP=nnn(text), SYSID=ssssCICS reported an error (EIBRESP) when attempting to read item(iiiii) fromthe Temporary Storage Queue (qqqqqqqq).

BIMFTRDM-6 TS Queue: qqqqqqqq is busy, try laterAn ENQ is active for this Temporary Storage Queue indicating that it may bebeing updated by another application or transfer function. Try this requestagain later.

BIMFTRDM-7 Access Not AuthorizedThe requested transfer has been rejected because of an Access SecurityDefinition that has been specified for the category you are using.

BIMFTRDP-1 Entry not foundThe requested POWER report/job could not be found.

BIMFTRDP-2 (XPPC error message text)See descriptions of these messages below. They are documented asBIMFTRDP-22nn messages.

BIMFTRDP-2 Alter/Delete Failed(alter/delete command)(message from POWER)This message is generated if the Category used for the download is definedto alter or delete the POWER queue entry after the transfer has completed,and the alter/delete is rejected by POWER. Included in the message is theactual alter/delete command, and the message returned from POWER.Since the alter/delete action does not occur until after the transfer iscomplete, this message does not appear on the PC. It will only appear in the"Host Transfer Activity Log". Refer to section "Viewing The Host TransferActivity Log (FTRL) " on page 251 for more information.

BIMFTRDP-4 FCB(xxxxxxxx) not foundThe report was generated with FCB(xxxxxxxx). BIM-PC/TRANSFER couldnot find the FCB. The FCB is required to convert host carriage control to PCCRLF sequences.

BIMFTRDP-5 FCB(xxxxxxxx) invalidThe report was generated with FCB(xxxxxxxx). BIM-PC/TRANSFER couldnot find a valid format FCB of that name. The FCB is required to convert hostcarriage control to PC CRLF sequences.


Messages Page 413

BIMFTRDP-6 Access Not AuthorizedThe requested transfer has been rejected because of an Access SecurityDefinition that has been specified for the category you are using.

BIMFTRDP-99 Host Abend-xxxx detectedThe host application abended. Request technical assistance for this error.

BIMFTRDP-nnnn (common messages)These messages are described in the common message section “BIMFTRxx-nnnn Messages” starting on page 443.

BIMFTRDQ-1 Dataset not foundThe requested dataset could not be found.

BIMFTRDQ-2 Dataset could not be openedCheck for other error messages in the output message log that may indicatethe reason for the failure.

BIMFTRDQ-3 SYNAD error occurred on input(synad error text)An error occurred during the processing of an input dataset. The second lineof the message describes the specific type of error.

BIMFTRDQ-5 SYNAD error occurred on output(synad error text)An error occurred during the processing of an output dataset. The secondline of the message describes the specific type of error.

BIMFTRDQ-7 Allocation error,(allocation error text)An error has occurred while attempting to allocate the dataset. Refer to thesection “Allocation / Deallocation Errors” on page 452 for a description ofthe allocation error text.

BIMFTRDQ-8 De-allocation error,(de-allocation error text)An error has occurred while attempting to de-allocate the dataset. Refer tothe section “Allocation / Deallocation Errors” on page 452 for a descriptionof the de-allocation error text.

BIMFTRDQ-9 Abend xxx-xx during InputAn I/O abend error has occurred while reading from the dataset. Refer to theMVS System Codes manual for a description of xxx-xx.

BIMFTRDQ-10 Abend xxx-xx during OutputAn I/O abend error has occurred while writing to the dataset. Refer to theMVS System Codes manual for a description of xxx-xx. The most likely erroris an out-of-space condition.


Page 414 Messages

BIMFTRDQ-16 Requested Dataset is not QSAMThis driver can only process QSAM Datasets. These are datasets with aDSORG=PS.

BIMFTRDQ-17 Input line nnnnn, with a length of lllll,exceeds max of mmmmm for datasetYour PC file contains a line that is to long for this dataset. 'nnnnn' is the linenumber within the PC file containing the invalid line. 'lllll' is the length ofthat line, and 'mmmmm' is the maximum length allowed for the currentdataset.

BIMFTRDQ-20 Space Allocation required for DISP=NEW DatasetYou have specified a new dataset for uploading, but have not provided anyprimary allocation space.

BIMFTRDQ-21 Blksize required for DISP=NEW DatasetYou have specified a new dataset for uploading, but have not provided adataset blocksize.

BIMFTRDQ-22 Lrecl of lllll is not valid for a Blksize of bbbbb and a Recfm of xxYou have specified an Lrecl that is not valid for the specified Blksize andRecfm.

BIMFTRDQ-23 Blksize required for input DatasetYou have specified a dataset for downloading that was created without ablocksize. This dataset cannot be processed by BIM-PC/TRANSFER.

BIMFTRDQ-24 Lrecl exceeds maximum for driverThis dataset has a lrecl that is to large to be processed by this driver. Themaximum allowed is 29,900.

BIMFTRDQ-99 Host Abend-xxxx detectedThe host application abended. Request technical assistance for this error.

BIMFTRDR-1 Entry not foundThe requested VSE Library member could not be found.

BIMFTRDR-2 (message text from BIM-EDIT)(last command line given to BIM-EDIT)The requested transfer failed because of an error condition detected in BIM-EDIT. The second line of the message shows the BIM-EDIT command thatfailed.

BIMFTRDR-5 Invalid Lib.Slib, Only Slib can be genericThe requested query specified a generic "Lib". This is not supported. The full"Lib" must be provided because it is required to access a correspondingDLBL.


Messages Page 415

BIMFTRDR-6 Access Not AuthorizedThe requested transfer has been rejected because of an Access SecurityDefinition that has been specified for the category you are using.

BIMFTRDR-99 Host Abend-xxxx detectedThe host application abended. Request technical assistance for this error.

BIMFTRDT-1 Queue xxxx not foundThe requested CICS Transient datea queue could not be found.

BIMFTRDT-2 Only uploads supportedA download has been attempted from a CICS Transient Data Queue. This isnot supported.

BIMFTRDT-3 Maximum record length exceeded for this queueA record in your upload exceeds the maximum allowed for the current CICSTransient Data Queue.

BIMFTRDT-4 Queue xxxx not available, EIBRESP=nnnnnThe specified CICS Transient Data Queue could not be accessed. Refer to thesection “EIBRESP Codes” on page 455.

BIMFTRDV-1 Profile not foundThe requested VSAM Profile could not be found.

BIMFTRDV-2 Upload not allowed for profile xxxxxxxxThe requested VSAM Profile 'xxxxxxxx' has been defined for downloadsonly.

BIMFTRDV-3 Download not allowed for profile xxxxxxxxThe requested VSAM Profile 'xxxxxxxx' has been defined for uploads only.

BIMFTRDV-9 Dataset xxxxxxxx not supportedThe dataset 'xxxxxxxx' is not a VSAM dataset.

BIMFTRDV-10 Dataset xxxxxxxx not availableThe host could not access the dataset 'xxxxxxxx' . If you are running BIM-PC/TRANSFER in CICS, use CEMT to check the status of the dataset. It mustbe open and enabled.

BIMFTRDV-11 Dataset xxxxxxxx out of spaceThe dataset 'xxxxxxxx' is full. Contact the person responsible for BIM-PC/TRANSFER.


Page 416 Messages

BIMFTRDV-12 Dataset xxxxxxxx ffff access error nnnn (test) lllll RC=rc EC=eccluster.name(first 64-bytes of data record)The dataset 'xxxxxxxx' could not be accessed for function 'ffff' because oferror 'nnnn'. The error number is from the field EIBRESP, and is documentedin the section “EIBRESP Codes” on page 455. Most error numbers will bedisplayed in text form as (text). ‘lllll’ is the current record length. The RC andEC are from VSAM, and are only valid for ILLOGIC and IOERR.‘cluster.name’ will only be shown for transfers that specify it.If this error occurs during an upload, and it reports a LENGERR, and you areuploading to a fixed length VSAM dataset, then the most likely cause is theabsence of the "truncate" and "PADhh" Driver Data options on your VSAMCategory Definition. Refer to page 373 for more information.

BIMFTRDV-16 VSAM Allocation error,(allocation error text)An error has occurred while attempting to allocate the VSAM Cluster. Referto the section “Allocation / Deallocation Errors” on page 452 for adescription of the allocation error text.

BIMFTRDV-17 Cluster Name not allowed for this ProfileThe VSAM Profile on the host does not allow for a VSAM Clusterspecification. Refer to the section “BIMFTRDV - VSAM Dataset Driver (UsingProfiles)” on page 370 for rules on when the Cluster name is allowed.

BIMFTRDV-18 Dataset xxxxxxxx currently in useVSAM transfers with a Cluster name specification are single-threaded whenin a CICS environment. This dataset / FCT name is active in a transfer at thistime. Try the transfer again later.

BIMFTRDV-19 Access to Profile xxxxxxxx is not allowedThis VSAM Profile has been secured with a SECGRP. You have not beengiven access to the SECGRP via your host user definition.

BIMFTRDV-20 Access to this dataset is not allowed:cluster.nameEither your host user definition, or the VSAM Profile you are using has beendefined with Dataset Access definition list. The cluster name you havespecified for this transfer has not been defined as being valid.

BIMFTRDV-21 Module xxxxxxx not availableThe host could not access the Service Module 'xxxxxxxx' . If you are runningBIM-PC/TRANSFER in CICS, use CEMT to check the status of the module.

BIMFTRDV-22 VSAM De-allocation error,(de-allocation error text)An error has occurred while attempting to de-allocate the VSAM Cluster.Refer to the section “Allocation / Deallocation Errors” on page 452 for adescription of the de-allocation error text.


Messages Page 417

BIMFTRDV-99 Host Abend-xxxx detectedThe host application abended. Request technical assistance for this error.

BIMFTRDX-1 Script not foundThe requested Script could not be found.

BIMFTRDX-2 Script contains more than 400 linesThe host cannot process a script larger than 400 lines.

BIMFTRDX-3 Script contains lines longer than 72 charactersThe host cannot process a script with lines longer than 72 characters.

BIMFTRDX-4 Script already existsYou have attempted to upload a script that already exists, and you did notspecify 'replace' on the transfer.

BIMFTRDX-5 Script does not end with a #ENDThe last line of all scripts must be a #END statement, starting in column 1.Correct the script and re-transfer.

BIMFTRDX-6 Access Not AuthorizedThe requested transfer has been rejected because of an Access SecurityDefinition that has been specified for the category you are using.

BIMFTRDX-10 Dataset xxxxxxxx not availableThe host could not access the dataset 'xxxxxxxx' . If you are running BIM-PC/TRANSFER in CICS, use CEMT to check the status of the dataset. It mustbe open and enabled.

BIMFTRDX-11 Dataset xxxxxxxx out of spaceThe dataset 'xxxxxxxx' is full. Contact the person responsible for BIM-PC/TRANSFER.

BIMFTRDX-12 Dataset xxxxxxxx access error nnnnThe dataset 'xxxxxxxx' could not be accessed because of error 'nnnn'. Theerror number is from the field EIBRESP, and is documented in the section“EIBRESP Codes” on page 455.

BIMFTRDX-99 Host Abend-xxxx detectedThe host application abended. Request technical assistance for this error.

BIMFTRHC-1 Script not found (xxxxxxxxxxxxxxxx)The requested HOSTAFT script could not be found in the Host Control File.


Page 418 Messages

BIMFTRHC-2 No #SENDTO found in script (xxxxxxxxxxxxxxxx)The specified HOSTAFT script does not contain a #SENDTO statement. Thisstatement is required so that BIM-PC/TRANSFER can determine which PC'sare to receive the script for processing.

BIMFTRHC-3 Too many netnames in script (xxxxxxxxxxxxxxxx)BIM-PC/TRANSFER can direct a HOSTAFT script to a maximum of 128PC's. If you need more than 128, you must divide the PC's between multiplescripts and schedule them all to be processed.

BIMFTRHC-4 Unknown ENDHOST state - xxxxxxxxThis is an internal error. Request technical support for this error.

BIMFTRHC-5 #ID xxxxxxx not foundThis is an internal error. Request technical support for this error.

BIMFTRHC-6 Netname xxxxxxx not found in #ID xxxxxxxUnless you have more than one person performing maintenance on aHOSTAFT status entry, then this is an internal error. Refresh your displayand try the command again. If the problem reoccurs, request technicalsupport for this error.

BIMFTRHC-7 Unknown caller id (xxxxxxxx)If this message is received by an application program you have written toactivate a HOSTAFT script, then the beginning of the COMMAREA does notbegin with 'HOSTAFT ', otherwise request technical support for this error.

BIMFTRHC-10 Dataset xxxxxxxx not availableThe host could not access the dataset 'xxxxxxxx' . If you are running BIM-PC/TRANSFER in CICS, use CEMT to check the status of the dataset. It mustbe open and enabled.

BIMFTRHC-11 Dataset xxxxxxxx out of spaceThe dataset 'xxxxxxxx' is full. The BIM-PC/TRANSFER Host Control file isfull. HOSTAFT transfers require space in the control file to keep track of theprogress of these transfers. Use the FTRM transaction to check for completedHOSTAFT transfers that can be deleted from the file. If none can be deleted,you will need to expand this dataset. Refer to section "Monitoring HOSTAFTStatus" on page 160 for more information.

BIMFTRHC-12 Dataset xxxxxxxx access error nnnnThe dataset 'xxxxxxxx' could not be accessed because of error 'nnnn'. Theerror number is from the field EIBRESP, and is documented in the section“EIBRESP Codes” on page 455.

BIMFTRHC-19 Module xxxxxxxx not availableThe host could not access the program module 'xxxxxxxx' . If you are runningBIM-PC/TRANSFER in CICS, use CEMT to check the status of the program.


Messages Page 419

BIMFTRHC-20 Errors occurred during script processingThis message will be generated if the WAIT option is specified for aHOSTAFT activation request, and an error occurred during the scriptprocessing. You can determine the actual error by using the FTRM hosttransaction to view the HOSTAFT status detail record for this script.

BIMFTRHC-21 Status record was deleted before completionThis message will be generated if the WAIT option is specified for aHOSTAFT activation request, and the HOSTAFT status detail record for thisscript is deleted using the FTRM host transaction before processing hascompleted.

BIMFTRI1-1 Driver xxxxxxxx not availableThe host could not access the driver 'xxxxxxxx' . If you are running BIM-PC/TRANSFER in CICS, use CEMT to check the status of the driver.

BIMFTRI1-2 INITIATE BIM-PC/TRANSFER ON YOUR PC. PRESS PF3 TO RETURN TO BIM-TMANMENUThis message is displayed when you select transaction FTRT from a BIM-TMAN menu. When this message is displayed, the BIM-TMAN session isready to communicate with BIM-PC/TRANSFER. “Hot key” to your PCsession and initiate BIM-PC/TRANSFER on the PC. When you havecompleted your transfers, “hot key” back to this screen and press PF3 toreturn to the BIM-TMAN menu screen.

BIMFTRI2-1 MODULE xxxxxxxx NOT AVAILABLE, EIBRESP=nnnThe host could not access the module 'xxxxxxxx' . If you are running BIM-PC/TRANSFER in CICS, use CEMT to check the status of the module. Thismessage is displayed on the system console.

BIMFTRI2-2 INVALID EYECATCHER xxxxxxxxAn invalid buffer was received from program BIMFTRIP. This message isdisplayed on the system console. Contact BIM Technical Support.

BIMFTRI2-3 MODULE BIMFTR92 NOT FOUND, EIBRESP=nnnThe host could not access the module TCP/IP for VSE interface moduleBIMFTR92 . If you are running BIM-PC/TRANSFER in CICS, use CEMT tocheck the status of the module.

BIMFTRI2-5 UNKNOWN BUFFER TYPE CODE=xxAn invalid buffer was received from the PC. This message is displayed onthe system console. Contact BIM Technical Support.

BIMFTRI2-6 INVALID COMMAND LENGTH FIELDAn invalid buffer was received from the PC. This message is displayed onthe system console. Contact BIM Technical Support.


Page 420 Messages

BIMFTRI2-8 TRANSACTION NOT VALID FROM TERMINALThis message is displayed if you enter the tranid defined for programBIMFTRI2 from a terminal.

BIMFTRIP-4 LISTENING AT IP ADDR nnn.nnn.nnn.nnn:ppppThis message is displayed on the system console when program BIMFTRIPhas activated a ‘Listen’ connection with the TCPIP partition.

BIMFTRIP-5 TCP/IP ACCESS ERROR ON nnn.nnn.nnn.nnn:pppp FN/RC=rr/ccThis message is displayed on the system console when an error is returnedfroma TCP/IP SOCKET request. The following values can be returned forFN/RC:0/0 User Requested Termination1/0 Open, Successful Execution1/4 Open, Not Established2/0 Close, Successful Execution2/4 Close, Connection Not Found3/0 Send, Successful Execution3/4 Send, Connection Not Found3/8 Send, IP Address Not Found3/12 Send, Execution Failure4/0 Receive, Successful Execution4/4 Receive, Connection Not Found4/8 Receive, Connection Was Reset5/0 Status, OK5/4 Status, Connection Not Found5/8 Status, Error6/0 Abort, OK6/16 Abort, Error

BIMFTRIP-6 TCP/IP TERMINATED ON nnn.nnn.nnn.nnn:ppppThis message is displayed on the system console when the TCP/IP ‘Listen’task has been stopped normally.

BIMFTRIP-7 TCP/IP CONNECTION ENDED BY USER nnn.nnn.nnn.nnn:ppppThis message is displayed on the system console when a TCP/IP connectionhas been terminated.

BIMFTRIP-8 TCP/IP NOT ACTIVE, IN 15 SECOND CONNECTION LOOP, DO YOU WISH TOSTOP? Y/NThis message is displayed when the transaction FTRP is entered on aterminal. It indicates that the BIMFTRIP ‘Listen’ task is currently waiting forthe TCP/IP partition to come active. If you wish the wait to continue,overtype the ‘N’ at the beginning of the message with a ‘Y and press ENTER.If you wish to terminate the ‘Listen’ task, simply press ENTER.


Messages Page 421

BIMFTRIP-9 WAITING FOR CONNECTION, DO YOU WISH TO STOP? Y/NTCP/IP WAITING ON ADDRESS nnn.nnn.nnn.nnn:ppppThis message is displayed when the transaction FTRP is entered on aterminal. It indicates that the BIMFTRIP ‘Listen’ task is currently waiting fora connection from a PC. If you wish the wait to continue, overtype the ‘N’ atthe beginning of the message with a ‘Y and press ENTER. If you wish toterminate the ‘Listen’ task, simply press ENTER.

BIMFTRIP-10 DATASET xxxxxxxx NOT AVAILABLEProgram BIMFTRIP could not access the dataset 'xxxxxxxx' . If you arerunning BIM-PC/TRANSFER in CICS, use CEMT to check the status of thedataset. It must be open and enabled.

BIMFTRIP-11 TCP/IP CONNECTION BY nnn.nnn.nnn.nnn:ppppThis message is displayed on the system console when a TCP/IP connectionhas been established.

BIMFTRIP-12 DATASET xxxxxxxx ACCESS ERROR eibresp - recordkey - eibretnThe dataset 'xxxxxxxx' could not be accessed because of error 'eibresp'. Seesection “EIBRESP Codes” on page 455.

BIMFTRSM-1 Remote File Access not supported by this release of CICSRemote file access requires CICS/VSE release 2.2 and above, or CICS/MVSrelease 3.3 and above.

BIMFTRSM-2 Error nnnn,nnnn attempting to link to pppppppp on CICS System ssssThe host could not link to the CICS System sysid ‘ssss’ to inquire on a remotefile. Make sure program ‘pppppppp’ is defined to CICS in the remote system.Common error codes are:0027,0000 PGMIDER0053,0018 SYSIDERR

BIMFTRSM-3 File xxxxxxxx not found in FCTFile ‘xxxxxxxx’ has not been defined to CICS.

BIMFTRSM-4 File xxxxxxxx not Authorized for AccessCICS security has rejected access to File ‘xxxxxxxx’.

BIMFTRSM-5 Wrong CALEN for pppppppp in ssssssssYour system has differant release levels of BIMFTRSM in various CICSpartitions/regions. ‘ssssssss’ is the applid of the CICS with a differantversion.

BIMFTRSM-6 Wrong release for pppppppp in ssssssssYour system has differant release levels of BIMFTRSM in various CICSpartitions/regions. ‘ssssssss’ is the applid of the CICS with a differantversion.


Page 422 Messages

BIMFTRSM-7 (error text),ddname,dsnameThis message is generated if an error occurs while attempting to extractinformation about a VSAM dataset from your VSAM catalog. (error text) willcontain a description of the type of access error:DD/DLBL NOT FOUNDCAT=xxxxxxx NOT FOUNDDATASET NOT FOUND IN CATALOGERROR OBTAINING CATALOG ACBCATLG ERROR - xxxxxxxxxxxxxxx

ddname is the dd/dlbl name being used to access the dataset information.dsname is the cluster name being used to access the dataset information.

BIMFTRXP-251 SCRIPT RECORD(xxxxxxxxxx), FOUND IN CF(ffffffff) DOES NOT HAVE VALIDDATA. PROCESSING ABORTEDThis message will be displayed on the CICS message log, the system consoleand returned to the workstation of origin when the script record appears tobe damaged. Delete and redefine the script, or restore the control file from abackup.

BIMFTRXP-254 SCRIPT RECORD(xxxxxxxxxx), WAS NOT FOUND IN CF(ffffffff). PROCESSINGABORTEDThis message will be displayed on the CICS message log, the system consoleand returned to the workstation of origin when the script record defined inthe VSAM profile cannot be found on the control file “ffffffff”. Rebuild thescript definition and add it to the control file and re-initiate the request.

BIMFTRXP-256 ACCESS TO CF(ffffffff) FAILED, REASON=(rrrrrrrrr), PROCESSING ABORTEDThis message will be displayed on the CICS message log, the system consoleand returned to the workstation of origin when an access to the control file“ffffffff” has failed for the reason given. The reason “rrrr” is translated fromthe returned VSAM return codes. Correct the problem identified and re-initiate the request.

BIMFTRXP-257 INVALID CONTROL TYPE CHARACTER FOUND IN SCRIPT LINE <nnnnn>This message will be returned to the workstation of origin when scriptprocessing finds an invalid control character in the first position of the scriptline. Processing is terminated at that point. Identify the script line and correctthe error and re-initiate.

BIMFTRXP-258 PROMPT (nnnn) PROCESSING FOUND ERROR IN NUMBER OF PROMPTS ANDRESPONSES, PROCESSING ABORTEDThis message will be displayed on the CICS message log, the system consoleand returned to the workstation of origin when script record “PROMPT”lines do not all receive responses from the Workstation. This may indicatethat the responses did not return properly to the host or that all presentedlists were not acted upon by the Workstation. Determine where the short falloccurred and correct the responses given.


Messages Page 423

BIMFTRXP-259 INVALID FIELD TYPE IDENTIFIER FOUND IN SCRIPT LINE <nnnnn>This message will be returned to the workstation of origin when scriptprocessing finds an invalid record field type identifier in the script line.Processing is terminated at that point. Identify the script line and correct theerror and re-initiate.

BIMFTRXP-260 LOGICAL ERROR FOUND IN SCRIPT LINE <nnnnn>This message will be displayed on the CICS message log, the system consoleand returned to the workstation of origin when script record line processinghas found a condition that does not make logical sense. This may indicatethat a referenced variable is not previously defined or something of thatnature. Examine the script record at line number given to determine whatmight be the problem. Correct the script and re-initiate the request.

BIMFTRXP-261 INVALID DATA, COMPARAND MUST BE NUMERIC VALUE SCRIPT LINE<nnnnn>This message will be returned to the workstation of origin when scriptprocessing finds invalid data following a relational condition requesting atest on a numeric field. Identify the script line and correct the error and re-initiate.

BIMFTRXP-262 LOGICAL ERROR FOUND IN PROMPT, SCRIPT LINE <nnnnn>This message will be displayed on the CICS message log, the system consoleand returned to the workstation of origin when script record line processinghas found a condition that does not make logical sense. This may indicatethat a referenced variable is not previously defined or something of thatnature. Examine the script record at line number given to determine whatmight be the problem. Correct the script and re-initiate the request.

BIMFTRXP-263 AN INVALID KEYWORD OPERAND (xxxxxxxx) WAS FOUND ON SCRIPT LINE<nnnnn>This message will be returned to the workstation of origin when scriptprocessing finds an invalid character string rather than the keyword “KEY”to identify the record field as a key field. Processing is terminated at thatpoint. Identify the script line and correct the error and re-initiate.

BIMFTRXP-264 VARIABLE SUBSTITUTION FOUND FOR ELEMENT BEFORE PROMPT LINEDEFINING IT. SCRIPT LINE <nnnn>.This message will be displayed on the CICS message log, the system consoleand returned to the workstation of origin when script record line processinghas found a variable substitution symbol in a script line before the PROMPTline defining the symbol. Examine the script record at line number given todetermine what might be the problem. Correct the script and re-initiate therequest.

BIMFTRXP-265 SCRIPT IF CLAUSE DOES NOT CONTAIN A BRANCH TO LABEL. SCRIPT LINE<nnnnn>This message will be returned to the workstation of origin when script recordline processing has found a missing 'required' element in a script line.


Page 424 Messages

Examine the script record at the line number given and provide the requiredvalue.

BIMFTRXP-266 NO RESPONSE LENGTH FIELD FOUND IN PROMPT LINE: SCRIPT LINE <nnnnn>This message will be displayed on the CICS message log, the system consoleand returned to the workstation of origin when script record line processinghas found a missing “required” element in a PROMPT line. The script lineindicated is the beginning line of the PROMPT line. Examine the scriptrecord at line number given and provide the required value.

BIMFTRXP-268 RESOLUTION OF VARIABLE AND/OR PROMPT ENTRIES FAILED SCRIPT LINE<nnnnn>This message will be returned to the workstation of origin when scriptprocessing cannot find a field variable name that in the variable table builtfrom the field names and prompt entries provided. Processing is terminatedat that point. Identify the script line and correct the error and re-initiate.

BIMFTRXP-270 VARIABLE ENTRY NOT FOUND IN VAR-TABLE FOR ENTRIES, SCRIPT LINE<nnnnn>This message will be returned to the workstation of origin when scriptprocessing cannot find a field variable name that in the variable table builtfrom the field names and prompt entries provided. Processing is terminatedat that point. Identify the script line and correct the error and re-initiate.

BIMFTRXP-272 NUMERIC COMPARAND TYPE UNDETERMINED FOR VALUE IN SCRIPT LINE<nnnnn>This message will be returned to the workstation of origin when scriptprocessing finds an entry that is not a character field, but is not identified as anumeric, packed or binary field. Processing is terminated at that point.Identify the script line and correct the error and re-initiate.

BIMFTRXP-273 FIELD LENGTH VALUE FOUND IS INVALID OR NOT NUMERIC. SCRIPT LINE<nnnnn>This message will be returned to the workstation of origin when scriptprocessing cannot find a valid field length entry . Processing is terminated atthis point.

BIMFTRXP-274 INVALID CONVERSION REQUEST FOUND FOR ENTRY IN SCRIPT LINE <nnnnn>This message will be returned to the workstation of origin when scriptprocessing finds a conversion request character that is not defined in themanual. Processing is terminated at that point. Identify the script line andcorrect the error and re-initiate.

BIMFTRXP-275 FIELD ENTRY LENGTH VALUE NOT FOUND AS EXPECTED. SCRIPT LINE <nnnnn>This message will be returned to the workstation of origin when scriptprocessing cannot find a valid field length entry in the expected relativescript line position . Processing is terminated at this point.


Messages Page 425

BIMFTRXP-276 INVALID RELATIONAL CONDITION TEST FOUND IN ENTRY FOR SCRIPT LINE<nnnnn>This message will be returned to the workstation of origin when scriptprocessing finds a relational condition character that is not defined in themanual. Processing is terminated at that point. Identify the script line andcorrect the error and re-initiate.

BIMFTRXP-277 FIELD OFFSET VALUE NOT NUMERIC AND NOT DYNAMIC. SCRIPT LINE<nnnnn>This message will be returned to the workstation of origin when scriptprocessing cannot find a valid field offset entry in the expected relative scriptline position. Processing is terminated at this point.

BIMFTRXP-278 INVALID KEYWORD FOUND IN OPTIONS STATEMENT FOR SCRIPT LINE<nnnnn>This message will be returned to the workstation of origin when scriptprocessing finds a keyword field that is not defined in the manual.Processing is terminated at that point. Identify the script line and correct theerror and re-initiate.

BIMFTRXP-279 FIELD ENTRY CONVERSION REQUEST FIELD NOT FOUND. SCRIPT LINE <nnnnn>This message will be returned to the workstation of origin when scriptprocessing cannot find a valid conversion request value in the expectedrelative script line position. Processing is terminated at this point.

BIMFTRXP-280 GROUP-BEGIN ENTRY OCCURS/REPEAT VALUE FIELD NOT FOUND. SCRIPT LINE<nnnnn>This message will be returned to the workstation of origin when scriptprocessing cannot find a valid occurs variable name or a numeric value forrepeat processing at the expected relative script line position. Processing isterminated at this point.

BIMFTRXP-281 CONTROL CARD NOT PROPERLY IDENTIFIED WITH '#' CHAR, SCRIPT LINE<nnnnn>This message will be returned to the workstation of origin when scriptprocessing identifies a control card that might be a reserved word but doesnot have the '#' sign identifier preceding it. Processing terminates at thispoint.

BIMFTRXP-282 INVALID '#' CONTROL CARD FOUND IN SCRIPT AT SCRIPT LINE <nnnnn>This message will be returned to the workstation of origin when scriptprocessing identifies a control card that is supposed to be a reserved wordbut is not. Processing terminates at this point.

BIMFTRXP-283 BRANCH TO LABEL DOES NOT HAVE CONTROL CARD ENTRY, SCRIPT LINE<nnnnn>This message will be returned to the workstation of origin when scriptprocessing identifies a control card that is a GOTO or IF statement that


Page 426 Messages

contains a label entry that is not found in previous or subsequent script lineentries. Processing terminates at this point.

BIMFTRXP-305 (error text) Current Record Key: kkkkkThis message will be returned to the workstation of origin when scriptprocessing encounters a #ERROR request. The (error text) is from the#ERROR statement. Processing is terminated at this point.

BIMFTRXP-310 INVALID SCRIPT TABLE OFFSET ABOUT LINE xxxxx, ABORTED.This message will be returned to the workstation of origin when scriptprocessing cannot identify the next sequential action to be executed. Thismessage may indicated that memory corruption has occurred, possibly over-writing elements of the script processing table, or a branch to label commandwas not properly resolved. If this message occurs, re-initiate the request todetermine if the script processing is corrupting itself or the problem wascreated by another application. If the error occurs again, or anotherBIMFTRXP- message is given, examine the script to determine if all offsetshave been correctly recorded. Correct errors and re-initiate.

BIMFTRXP-311 GROUP PROCESSING REPEAT VALUE ERROR FOUND, ON LINE xxxxx,ABORTED.This message will be returned to the workstation of origin when scriptprocessing finds a variable value on the GROUPBEG entry that does notmeet the requirements of a numeric field. This message may indicate that thefield offset given in the script line is incorrect, or that the field does notcontain a numeric value. Examine the script line identified and correct theoffset if necessary or examine the value in the record to determine if fileintegrity has been compromised. Correct errors and re-initiate.

BIMFTRXP-312 EBCDIC/ASCII CONVERSION TYPE MISMATCH FOUND ON LINE xxxxx,ABORTED.This message will be returned to the workstation of origin when scriptprocessing finds a variable value given in a script line that does not matchthe requirements for data type and the requested conversion required. Thismay indicate that the field offset given in the script line is incorrect, or thatthe field does not contain a numeric value. Examine the script line identifiedand correct the offset if necessary or examine the value in the record todetermine if file integrity has been compromised. Correct errors and re-initiate.

BIMFTRXP-313 NUMERIC CONVERISON TYPE MISMATCH FOUND, ON LINE xxxxx, ABORTED.This message will be returned to the workstation of origin when scriptprocessing finds a variable value given in a script line that does not matchthe requirements for data type and the requested conversion required. Thismay indicate that the field offset given in the script line is incorrect, or thatthe field does not contain a numeric value. Examine the script line identifiedand correct the offset if necessary or examine the value in the record todetermine if file integrity has been compromised. Correct errors and re-initiate.


Messages Page 427

BIMFTRXP-314 NUMERIC PRECISION PROCESSING ERROR FOUND, ON LINE xxxxx, ABORTED.This message will be returned to the workstation of origin when scriptprocessing finds a variable value given in a script line that does not matchthe requirements for data type and the requested conversion required. Thismay indicate that the field offset given in the script line is incorrect, or thatthe field does not contain a numeric value. Examine the script line identifiedand correct the offset if necessary or examine the value in the record todetermine if file integrity has been compromised. Correct errors and re-initiate.

BIMFTRXP-315 PROCESSING TABLE HAS BEEN CORRUPTED, PROCESSING IS ABORTED.This message will be returned to the workstation of origin when examinationof memory addresses does not match values expected. This may occur ifmemory is over-written by this application or by other applications duringthe running time of the file transfer. If this message occurs, re-initiate therequest to determine if the script processing is corrupting itself or theproblem was created by another application. If the error occurs again, oranother BIMFTRXP- message is given, examine the script to determine if alloffsets have been correctly recorded. Correct errors and re-initiate.

BIMFTRXP-316 CONVERSION TYPE NOT DETERMINED FOR NUMERIC TYPES, ON LINE xxxxx,ABORTED.This message will be returned to the workstation of origin when scriptprocessing finds a variable value given in a script line that does not matchthe requirements for data type and the requested conversion required. Thismay indicate that the field offset given in the script line is incorrect, or thatthe field does not contain a numeric value. Examine the script line identifiedand correct the offset if necessary or examine the value in the record todetermine if file integrity has been compromised. Correct errors and re-initiate.

BIMFTRXP-317 BINARY FIELD LENGTH VALUE GREATER THAN FOUR BYTES, ON LINE xxxxx,ABORTED.This message will be returned to the workstation of origin when scriptprocessing finds a variable value given in a script line that contains a lengthfield larger than allowed for a binary field. Examine the script line identifiedand correct the field length as necessary and re-initiate.

BIMFTRXP-318 INVALID PACKED DATA FIELD FOUND WITH INFORMATION ON LINE xxxxx,ABORTED.This message will be returned to the workstation of origin when scriptprocessing finds a variable value given in a script line that does not matchthe requirements for data type given on the script line. This may indicate thatthe field offset given in the script line is incorrect, or that the field does notcontain a packed numeric value. Examine the script line identified andcorrect the offset if necessary or examine the value in the record to determineif file integrity has been compromised. Correct errors and re-initiate.


Page 428 Messages

BIMFTRXP-319 ABORTED, OUTPUT SPACE OVER-RUN LINE xxxx, RECORD:This message will be returned to the workstation of origin when scriptprocessing finds a variable value given in a script line that generates loopprocessing that eventually fills the communication buffer. Processing isaborted to prevent storage corruption. Examine the script line given todetermine if the offset to an “OCCURS” variable might be incorrect or thatthe GROUP might contain more data than allowable space can hold.

BIMFTRXP-320 CALCULATED OFFSETS EXCEED GIVEN RECORD LENGTH, ON LINE xxxxx,ABORTED.This message will be returned to the workstation of origin when scriptprocessing determines that given or calculated offsets have exceeded thelength of the record it is extracting from. Processing is aborted to preventstorage corruption. Examine the script line given to determine why offsetsmight have exceeded the length of the record. Correct errors and re-initiate.

BIMFTRXP-321 ERROR MSG PROCESSING FAILED TO FIND LINE BREAK, ON LINE xxxxx,ABORTED.This message will be returned to the workstation of origination when scriptprocessing of a script error line cannot find a place to break the message intodisplayable lengths for display in a dialog box. Processing is aborted toprevent storage corruption. Examine the script line given to determine whyline breaks cannot be obtained logically. Correct errors or shorten errormessage and re-initiate.

BIMFTR92-1 TCP/IP FAILURE ON IP=nnn.nnn.nnn.nnn,port, FC=x, R15=n, SRCODE=nA function(FC=) of (S)end or (R)eceive was rejected by the TCP/IP for VSEinterface. Request technical assistance for this message.

BIMFTR92-2 INVALID FUNCTION=nnn(xxx)This is an internal logic error. Request technical assistance for this message.

BIMFTR98-1 IDCAMS Definition (xxxxxxx) Not FoundIDCAMS Definitions must be defined in the BIM-PC/TRANSFER hostcontrol file(BIMFTRF) as a 'Script Definition'.

BIMFTR98-2 IDCAMS Definition (xxxxxxx) does not begin with (#IDCAMS) or end with(#END)IDCAMS Definitions must begin with a #IDCAMS line, and end with a#END line. Refer to the section on driver BIMFTRDC beginning on page 315for more information about IDCAMS Definitions.

BIMFTR98-3 DLBL for Catalog (catname) Not FoundThe PC user has specified the DLBL name of a VSAM Catalog, but no DLBLcan be found in either the CICS or BIM-TMAN JCL, or standard/partitionlabels.


Messages Page 429

BIMFTR98-4 Variable Substitution Overflow on line nnnof IDCAMS Definition (xxxxxxx)The specified IDCAMS Definition contains substitution variable(s) on linennn of the script definition. The data being replaced for the variable willcause part of the IDCAMS command to move beyond column 72. You willneed to rework the definition to place less data on the line in error. Refer tothe section on driver BIMFTRDC beginning on page 315 for moreinformation about IDCAMS Definitions and substitution variables.

BIMFTR98-5 IDCAMS Definition (xxxxxxx) exceeds max of nnn linesIDCAMS Definitions must not be longer than nnn lines in length.

BIMFTR98-6 IDCAMS Error Response RC=nnnDuring Processing of IDCAMS Definition (xxxxxxx)The following messages were returned:(messages from IDCAMS)This message will be generated if IDCAMS completes with a return codegreater than the max specified in the IDCAMS Definition via the #MAXCC=statement. Any non-informational messages from IDCAMS will be includedat the end of this message. Refer to the section on driver BIMFTRDCbeginning on page 315 for more information.

BIMFTR98-7 Dataset Access error on (xxxxxxx), Resp=nnnnThe dataset (xxxxxxxx) could not be accessed because of error 'nnnn'. Theerror number is from the field EIBRESP, and is documented in the section“EIBRESP Codes” on page 455.

BIMFTR98-8 CDLOAD for IDCAMS failed, RC=nnnThis will normally occur if your CICS or BIM-TMAN partition does not haveenough free GETVIS area to load IDCAMS Make sure you have at least 200Kof available GETVIS.

BIMFTR98-9 Subtask Abend has occurredRequest BIM Technical Assistance for this message.

BIMFTR98-10 Specified Record Size of nnnnn,Exceeds Max allowed of mmmmmThe specified record size exceeds the maximum allowed by VSAM.

BIMFTR98-11 Calculated Block Size of nnnnn (recsz*blkfactor),Exceeds Max allowed of mmmmmThe calculated block size for this fixed blocked dataset exceeds the maximumallowed by VSAM.

BIMFTR98-12 Invalid Record Format Specified (recfm)The valid Record Formats are: Fixed, Variable, and Undef.


Page 430 Messages

BIMFTR98-13 Specified Record Size of nnnnn,Exceeds Max allowed of mmmmmby IDCAMS Definition (xxxxxxx)A maxim allowed record size has been defined for this IDCAMS Definitionvia the #RECSZ= statement.

BIMFTR98-14 Specified Nbr Records to Allocate of nnnnn,Exceeds Max allowed of mmmmmby IDCAMS Definition (xxxxxxx)A maxim allowed number of records to allocate has been defined for thisIDCAMS Definition via the #NRECS= statement.

BIMFTR98-15 Specified Catalog DLBL Name (catname) is not allowedby IDCAMS Definition (xxxxxxx)This IDCAMS Definition has restricted the (catname) usage via the #VOL=statement.

BIMFTR98-16 Invalid #VOL command, reason (n),found in IDCAMS Definition (xxxxxxxx)(invalid #vol command)The syntax of the #VOL command is not valid. Reasons are:1 Imbedded blank found in command.2 catname field is to long or not followed by a '('.3 Volser list not terminated by a ')'.4 No Volsers found between '(' and ')'.

BIMFTR98-17 #keyword command after first IDCAMS command,found in IDCAMS Definition (xxxxxxxx)(command)All #keyword commands must be position at the front of the IDCAMSDefinition, prior to the first IDCAMS command.

BIMFTR98-18 Unknown #keyword command,found in IDCAMS Definition (xxxxxxxx)(unknown command)This command is invalid. Refer to the section on driver BIMFTRDCbeginning on page 315 for more information on IDCAMS Definitions.

BIMFTR98-19 No IDCAMS commands found in (xxxxxxxx)This IDCAMS Definition (xxxxxxxx) does not appear to contain anycommands for IDCAMS. Refer to the section on driver BIMFTRDC beginningon page 315 for more information on IDCAMS Definitions.

BIMFTR99-1 Module xxxxxxx not available to driver zzzzzzzzThe host could not access the Script Processing Module 'xxxxxxxx' . If you arerunning BIM-PC/TRANSFER in CICS, use CEMT to check the status of themodule.


Messages Page 431

BIMFTR99-2 Exit xxxxxxx not available to driver zzzzzzzzThe host could not access the Formatting/Selection exit 'xxxxxxxx' . If you arerunning BIM-PC/TRANSFER in CICS, use CEMT to check the status of theexit.

BIMFTR99-3 Dataset xxxxxxxx ffff access error nnnn(text)Resp2=rrrrr, Rcode=xxxxxxxxxxxThe dataset 'xxxxxxxx' could not be accessed for function 'ffff' because oferror 'nnnn'. The error number is from the field EIBRESP, and is documentedin the section “EIBRESP Codes” on page 455.

BIMFTR99-4 Access to this dataset is not allowed:dataset.nameYour host user definition has been defined with a Dataset Access definitionlist. The dataset name you have specified for this transfer has not beendefined as being valid.

BIMFTR99-5 Dataset/Mask must include first period:dataset.name.maskFor MVS, generic dataset names must at least include the high-level qualifierfor the catalog search routine.

BIMFTR99-6 Invalid Dataset Mask specification:dataset.name.maskThe dataset name that was specified contains characters that make inunrecognizable as a dataset name, PDS name or GDG name.


Page 432 Messages

FTRL Transaction Messages

BIMFTRLD-01 MAPSET xxxxxxxx NOT FOUND OR DISABLEDThe mapset used by the FTRL transaction could not be loaded. Check thestatus with CEMT and correct.

BIMFTRLD-02 ERROR nnnn FROM BMS FOR mapset,map,functionThis is an internal error. Request technical assistance for this message.

BIMFTRLD-03 END OF EVENTS TO DISPLAY.Informational message.

BIMFTRLD-10 DATASET xxxxxxx NOT AVAILABLEThe log file 'xxxxxxxx' could not be accessed in CICS. Use the CEMTtransaction to determine the status of the file. It must be OPEN andENABLED.

BIMFTRLD-12 DATASET xxxxxxx ACCESS ERROR nnnnnThe log file 'xxxxxxxx' could not be accessed in CICS. The value for 'nnnnn' isthe EIBRESP value returned by CICS, and is documented in the section“EIBRESP Codes” on page 455. Verify that the FCT definition conforms to thespecifications in the section “VSE Installation Step 6 - CICS/VS TableAdditions” starting on page 23, and section “MVS Installation Step 6 -CICS/VS Table Additions” starting on page 34. If they do, request technicalassistance for this message.


Messages Page 433

FTRM Transaction Messages

BIMFTRFT-01 MAPSET xxxxxxxx NOT FOUND OR DISABLEDThe mapset used by the FTRM transaction could not be loaded. Check thestatus with CEMT and correct.

BIMFTRFT-02 ERROR nnnn FROM BMS FOR mapset,map,functionThis is an internal error. Request technical assistance for this message.

BIMFTRFT-03 (type of record) HAS BEEN UPDATED.This is a confirmation message that the changes to the specified record typehas been made on the control file.

BIMFTRFT-04 (type of record) HAS BEEN ADDEDThis is a confirmation message that a new record of the specified type hasbeen added to the control file.

BIMFTRFT-05 (type of record) NOT FOUND, USE PF5 TO ADDYou have attempted to update a record that does not exist on the control file.This may be because you changed the contents of the key field. Refer to thesection “Adding / Changing Definitions” on page 187 for more information.

BIMFTRFT-06 (type of record) EXISTS, USE PF2 TO UPDATEYou have attempted to add a record that already exists on the control file.Refer to the section “Adding / Changing Definitions” on page 187 for moreinformation.

BIMFTRFT-07 END OF (type of record)SYou have pressed [PF8] when the last Definition of the specified type hasbeen displayed. Press [PF7] to scroll to the previous entry.

BIMFTRFT-08 (type of record) HAS BEEN DELETEDThis is a confirmation message that the specified record has been deletedfrom the control file. If [PF12] has been pressed by accident, press [PF5] to re-add the definition.

BIMFTRFT-09 (type of record) NOT FOUNDThis message is displayed if you attempt to delete a definition from a Listscreen, and the definition has already been deleted.


Page 434 Messages

BIMFTRFT-10 DATASET xxxxxxx NOT AVAILABLEThe control file 'xxxxxxxx' could not be accessed in CICS. Use the CEMTtransaction to determine the status of the file. It must be OPEN andENABLED.

BIMFTRFT-11 DATASET xxxxxxx IS OUT OF SPACEDefine more space for the control file.

BIMFTRFT-12 DATASET xxxxxxx ACCESS ERROR nnnnnThe control file 'xxxxxxxx' could not be accessed in CICS. The value for'nnnnn' is the EIBRESP value returned by CICS, and is documented in thesection “EIBRESP Codes” on page 455. Verify that the FCT definitionconforms to the specifications in the section “VSE Installation Step 6 -CICS/VS Table Additions” starting on page 23, and section “MVSInstallation Step 6 - CICS/VS Table Additions” starting on page 34. If theydo, request technical assistance for this message.

BIMFTRFT-13 CRLF and TRANSLATE MUST BE Y, N, OR *Specify either 'Y', 'N', or '*' for these fields.

BIMFTRFT-14 EXIT/DRIVER/TABLE NOT AVAILABLEThe values specified for EXIT, DRIVER and TRTABLE must be programsdefined to CICS, and must be ENABLED. Check the status with CEMT andcorrect.

BIMFTRFT-15 INVALID HEX DIGIT X'xx'You have entered an invalid hexadecimal digit in the START KEY or ENDKEY. Valid hexadecimal digits are '0' through '9' and 'A' through 'F'.

BIMFTRFT-16 INVALID CHARACTER 'c' IN PASSWORD.BIM-PC/TRANSFER does not support this character for use in passwords.All keyable characters except ',' ' ','_' and '-' are supported.

BIMFTRFT-17 USER DEFINITION OPTION MUST BE Y, N OR RSpecify either 'Y', 'N' or 'R' for this field.

BIMFTRFT-18 WARNING, SCRIPT DEFINITION HAS BEEN UPDATED AND NOT SAVEDYou have attempted leave the current script definition screen withoutupdating the control file with the current changes. If you wish to not save thechanges, repeat the function just attempted, otherwise press the appropriatePF key to add or update the script definition.

BIMFTRFT-19 ONLY DOWNLOADS SUPPORTED WITH VSAM SCRIPTSBIM-PC/TRANSFER does not currently support uploads during scriptprocessing.


Messages Page 435

BIMFTRFT-21 DATASET ACCESS DEFINITION NOT FOUND FOR (UP)BIMFTRFT-22 DATASET ACCESS DEFINITION NOT FOUND FOR (DN)

Dataset Access Definitions must be defined on the control file before they canbe referenced in a User Definition, or VSAM Profile.

BIMFTRFT-23 CLUSTER ONLY VALID WITH BIM$... DATASETThe CLUSTER field can only be specified if the name of the DATASET beginswith the characters 'BIM$'.

BIMFTRFT-24 EXIT/SCRIPT MUST BE X, S, OR NThe EXIT/SCRIPT field indicates which type of extra processing is to beperformed:N noneX Formatting/Selection ExitS Script.

BIMFTRFT-25 TRANSFER TYPE MUST BE U, D, OR BValid Transfer Types are: (U)pload, (D)ownload, (B)oth.

BIMFTRFT-26 END KEY LENGTH MUST BE 0 - 64The length of the END KEY must be a number in the range of 0 through 64.

BIMFTRFT-27 SPECIFIED OPTION MUST BE Y OR NThe hi-lighted option can only be specified as 'Y' or 'N'.

BIMFTRFT-28 SCRIPT AT MAX LENGTH AND MISSING #ENDVSAM scripts can contain up to 400 lines. They must also contain a #ENDstatement as their last line. The #END must begin in column 1.

BIMFTRFT-29 GEN LOG OPTION MUST BE Y OR NThe GENERATE EVENT LOG option must be specifed as ‘Y’ to generate thelog, or ‘N’ to not generate the log.

BIMFTRFT-31 HOSTAFT MODULE (nnnnnnnn) NOT AVAILABLEThe HOSTAFT control module (nnnnnnnn) must be defined to CICS as aprogram, and must be ENABLED. Check the status with CEMT and correct.

BIMFTRFT-32 NO LOG DATA AVAILABLE FOR THIS NETNAMEThis message is displayed if you enter the 'V' CMD on the HOSTAFT StatusDetail screen for a NETNAME entry with a status other than 'Script Error' or'Transfer Error'.

BIMFTRFT-33 ENTER NEW NETNAME IN HI-LIGHTED FIELDThis message is displayed when you enter the 'A' CMD on the HOSTAFTStatus Detail screen. This allows the addition of a new NETNAME to thecurrent HOSTAFT process. Enter the new NETNAME to be added and pressENTER.


Page 436 Messages

BIMFTRFT-34 REQUESTED HOSTAFT SCRIPT HAS BEEN ACTIVATEDThis message is displayed to confirm that the requested script has beenactivated, and is waiting for the PC inquiries.

BIMFTRFT-35 UPDATES NOT ALLOWEDThis message is displayed if you attempt to add, update, or delete a hostdefinition in a section for which your FTRx transaction has been giveninquiry access only. Use an FTRx transaction that has update access to thisdefinition.

BIMFTRFT-36 INVALID SECURITY LEVELThis message is displayed if you specify an invalid value for a LVL field.Refer to page 229 for a list of valid settings for the LVL field.

BIMFTRFT-37 CATGRP FIELD IS REQUIREDAll Access Security Definitions require a non-blank CATGRP name.

BIMFTRFT-38 PORT NBR MUST BE NUMERIC, 4096-65000The entered port number is not in the range of 4096 through 65000.

BIMFTRFT-39 SYSID MUST BE NUMERIC, 00-99The entered TCPIP system id is not in the range of 00 through 99.

BIMFTRFT-40 TRANID MUST BE DEFINED AND POINT TO BIMFTRI2Refer to the Installation Section for more information.

BIMFTRFT-41 TRANID MUST BE DEFINED AND POINT TO BIMFTRIPRefer to the Installation Section for more information.

BIMFTRFT-42 RECSIZE MUST BE 0-32000The entered RECSIZE is not in the range of 0 through 32000.

BIMFTRFT-43 BLKSIZE MUST BE 0-32761The entered BLKSIZE is not in the range of 0 through 32761.

BIMFTRFT-44 RECFORM MUST BE F, V, OR UThe entered RECFORM is not not valid.

BIMFTRFT-45 RECSIZE REQUIRED FOR RECFORM=FThe RECSIZE field is required for this record format.

BIMFTRFT-46 INVALID RECSIZE AND BLKSIZE COMBINATIONFor a fixed format file, the BLKSIZE must be a multiple of the RECSIZE.

BIMFTRFT-47 BLKSIZE IS REQUIRED FOR UPLOAD SUPPORTThe BLKSIZE field is required for uploads.


Messages Page 437

BIMFTRFT-48 SCRIPT NOT FOUNDThe specifed script name has not been defined using the FTRM transaction.

BIMFTRFT-49 DLBL AND BIM-EPIC DSN ARE MUTUALLY EXCLUSIVEYou can only specify one of these fields.

BIMFTRFT-50 DEFAULT USER DEFINITION NOT FOUNDThis message is displayed if you enter a User ID in field “DEFAULT USERDEFINITION” that has not yet been defined. Define the user first, and thenupdate this field.

BIMFTRFT-9998 WARNING - PRODUCT AUTHORIZATION EXPIRES IN 30 DAYS OR LESSThis message is displayed if the copy of BIM-PC/TRANSFER you are usingis about to expire. Contact your BIM product sales representative for a newExpiration Password.

BIMFTRFT-9999 PRODUCT AUTHORIZATION HAS EXPIREDBIM-PC/TRANSFER is protected with an Expiration Password. Thismessage is displayed if that Password has expired. Contact your BIMproduct sales representative for a new Expiration Password.


Page 438 Messages

BIMFTRBC Messages

BIMFTRBC-1 HOSTAFT COMMAND COMPLETED OKInformational message displayed on SYSLST/SYSPRINT at the end of aHOSTAFT command to indicate that the HOSTAFT script has been activated,and is ready to be contacted by the PC's defined in the script.

BIMFTRBC-2 NO ALLOCATED SESSION, FUNCTION TERMINATEDThis message is displayed on SYSLST/SYSPRINT if a HOSTAFT command isattempted without a valid APPC connection to CICS to BIM-TMAN. A priorCONNECT command is required to establish the connection. Refer to othergenerated errors for the cause of the connection failure.

BIMFTRBC-3 THE FOLLOWING ERROR OCCURRED, FUNCTION TERMINATEDThe BIM-PC/TRANSFER host system has returned an error message. It willbe printed following this message. Refer to the description for that errormessage for the cause and resolution of the problem.


Messages Page 439

BIMFTRLB Messages

BIMFTRLB-1 FUNCTION COMPLETEDInformational message displayed on SYSLST at the end of a command.

BIMFTRLB-2 BIMFTRLB RELEASE x.xx HAS BEEN ACTIVATED.Informational message displayed on SYSLST and the System Console eachtime the program is executed.

BIMFTRLB-3 BIMFTRLB HAS BEEN TERMINATEDInformational message displayed on SYSLST and the System Console whenan unexpected error occurs. A message will be displayed prior to thisexplaining the actual error.

BIMFTRLB-4 BIMFTRLB HAS BEEN TERMINATED VIA A STOP REQUESTInformational message displayed on SYSLST and the System Console when aSTOP command has been issued.

BIMFTRLB-5 LIBR NOT FOUNDBIMFTRLB could not load phase LIBR. Check your LIBDEF.

BIMFTRLB-6 ENTER STOP OR CONTINUEThis message is display on the System Console in response to a MSG ppoperator command. Respond 'STOP' to terminate the partition, or response'CONTINUE' or blanks to continue processing.

BIMFTRLB-nnnn (common messages)These messages are described in the common message section “BIMFTRxx-nnnn Messages” starting on page 443.


Page 440 Messages

BIMFTRFI Messages

BIMFTRFI-1 BIM-PC/TRANSFER RELEASE x.xx CONTROL FILE INITIALIZATION COMPLETEInformational message displayed on SYSLST and the System Console toindicate that the requested initialization has been completed.

BIMFTRFI-2 BIM-PC/TRANSFER RELEASE x.xx

LOG

CONTROL FILE INITIALIZATION FAILED

Message displayed on SYSLST and the System Console to indicate that therequested initialization has failed. One or more other messages will havebeen generated stating the specific reason for the failure. The jobstepcondition code is set to 12.

BIMFTRFI-3 VSAM ERROR ON FILE ‘dd/dlbl’(VSAM error text)KEY=‘record key in character’x’record key in hex’RRN=nnnnnMessage displayed on SYSLST when a VSAM error is detected. Requesttechnical assistance for this error.

BIMFTRFI-4 VSAM ERROR ON FILE ‘dd/dlbl’DUPLICATE RECORDKEY=‘record key in character’x’record key in hex’RRN=nnnnnMessage displayed on SYSLST when a VSAM duplicate record error isdetected. Delete/Define the file and retry initialize. If message occurs again,request technical assistance.

BIMFTRFI-5 NO INPUT COMMAND SPECIFIED, INITIALIZATION TERMINATEDMessage displayed on SYSLST and the System Console to indicate that noINITIALIZE command has been specified. The jobstep condition code is setto 12.

BIMFTRFI-6 BIM-PC/TRANSFER RELEASE x.xx LOG FILE INITIALIZATION COMPLETE, ROOMIN LOG FILE FOR nnnnn EVENTSInformational message displayed on SYSLST and the System Console toindicate that the requested log file initialization has been completed. Thismessage indicates the number of log reocords that can be placed in the filebefore a wrap condition begins.


Messages Page 441

BIMFTRFI-7 CATALOG ACCESS ERROR ON

LOG

CONTROL FILE "dlbl/ddname',FDBK=X'nnnn', REASON=X'nnnn',TEXT=descriptive text,DSN=cluster.name,CATALOG=catalog.nameMessage displayed on SYSLST to indicate that the VSAM catalog could notbe accessed for information about the specified file. Request technicalassistance.

BIMFTRFI-8

LOG

CONTROL FILE "dlbl/ddname' NOT FOUND IN CATALOG,FDBK=X'nnnn', REASON=X'nnnn',TEXT=descriptive text,DSN=cluster.name,CATALOG=catalog.nameMessage displayed on SYSLST to indicate that the specified file was notfound in your VSAM catalog. Check your IDCAMS DEFINE and your JCL tomake sure you have specified the proper cluster name.

BIMFTRFI-9

LOG

CONTROL FILE "dlbl/ddname' IS THE WRONG CLUSTER TYPE,SHOULD BE xxDS, IS DEFINED AS xxDS,DSN=cluster.name,CATALOG=catalog.nameMessage displayed on SYSLST to indicate that the specified file was definedincorrectly to VFSAM. Check your IDCAMS DEFINE against the sampleprovided in the installation section of this manual.

BIMFTRFI-10

LOG

CONTROL FILE "dlbl/ddname' HAS THE WRONG MAX RECLEN,SHOULD BE nnnnn, IS DEFINED AS nnnnn,DSN=cluster.name,CATALOG=catalog.nameMessage displayed on SYSLST to indicate that the specified file was definedincorrectly to VFSAM. Check your IDCAMS DEFINE against the sampleprovided in the installation section of this manual.

BIMFTRFI-11 CONTROL FILE "dlbl/ddname' HAS THE WRONG KEYS,SHOULD BE KEYS(n m), IS DEFINED AS KEYS(x y),DSN=cluster.name,CATALOG=catalog.nameMessage displayed on SYSLST to indicate that the specified file was definedincorrectly to VFSAM. Check your IDCAMS DEFINE against the sampleprovided in the installation section of this manual.

BIMFTRFI-nnnn (common messages)These messages are described in the common message section “BIMFTRxx-nnnn Messages” starting on page 443.


Page 442 Messages

BIMFTRPR Messages

BIMFTRPR-1 LOG FILE PRINT COMPLETE, n EVENTS READ, n EVENTS PRINTEDInformational message displayed on SYSLST to indicate that the requestedprint has been completed.

BIMFTRPR-2 NEWEVENTS PROCESSING WILL RESUME FOLLOWING THE EVENT THATOCCURRED ON mm/dd/yy AT hh:mm:ssInformational message displayed on SYSLST when either the NEWEVENTSor NEWEVENTSFINAL operand is specified. It dislays the date/time of therestart point for the new events.

BIMFTRPR-3 RESTART POINT LOST, NEWEVENTS OPTION IS IGNOREDInformational message displayed on SYSLST when either the NEWEVENTSor NEWEVENTSFINAL operand is specified and the activity log haswrapped the previous restart point. The print request will start with theoldest event currently in the activity log.

BIMFTRPR-4 RESTART POINT HAS BEEN UPDATED IN LOG FILEInformational message displayed on SYSLST when the NEWEVENTSFINALoperand is specified to confirm that the restart point has been updated forthe next print request.

BIMFTRPR-5 BIM-PC/TRANSFER RELEASE x.xx, LOG PRINT FAILEDMessage displayed on SYSLST and the System Console to indicate that therequested print has failed. One or more other messages will have beengenerated stating the specific reason for the failure. The jobstep conditioncode is set to 12.

BIMFTRPR-6 VSAM ERROR ON FILE ‘dd/dlbl’(VSAM error text)RRN=nnnnn, CURRENT=nnnnnMessage displayed on SYSLST when a VSAM error is detected. Requesttechnical assistance for this error.

BIMFTRPR-nnnn (common messages)These messages are described in the common message section “BIMFTRxx-nnnn Messages” starting on page 443.


Messages Page 443

BIMFTRxx-nnnn MessagesThe messages in this section are common to one or more components of BIM-PC/TRANSFER.

BIMFTRxx-1000 'x' IS AN INVALID COMMANDThe first word in the line, "x", is not a valid command. If it is a parameterintended to be part of a previous command, check for valid continuation onthe end of the previous line. If it is supposed to be part of a comment, checkfor the proper use of "/*" (start of comment),";" (end of command), andcontinueation characters.

BIMFTRxx-1001 'x' IS AN INVALID KEYWORD FOR 'y' SUB-PARAMETERS FOLLOWING IT AREIGNOREDThe character string "x" was specified as a sub-parameter of "y", and is not avalid keyword for "y". Any sub-parameters coded for "x" are ignored. If "x"was not intended to be a sub-parameter of "y", check your use of parentheses.If "x" is a command, a previous command may have been continuedimproperly.

BIMFTRxx-1002 'x' EXCEEDS THE NUMBER OF POSITIONAL PARAMETERS ALLOWED FOR 'y'SUB-PARAMETERS FOLLOWING IT ARE IGNOREDPositional parameters are allowed for "y", but the maximum number allowedhad already been specified before "x" was found. Any sub-parameters codedfor "x" are ignored. If "x" was not intended to be a sub-parameter of "y",check your use of parentheses. If "x" is a command, a previous commandmay have been continued improperly.

BIMFTRxx-1003 'x' IS INVALID - NO PARAMETERS ALLOWED FOR 'y'SUB-PARAMETERS FOLLOWING IT ARE IGNOREDNo sub-parameters are allowed for "y", but "x" was coded as a sub-parameter. Any sub-parameters coded for "x" are ignored. If "x" was notintended to be a sub-parameter of "y", check your use of parentheses.

BIMFTRxx-1004 'x' CAN BE SPECIFIED ONLY n TIMES FOR 'y'SUB-PARAMETERS FOLLOWING IT ARE IGNOREDA list of repeated sub-parameters (maximum of "n") are allowed for "y", but"x" exceeds this maximum. Any sub-parameters coded for "x" are ignored. If"x" was not intended to be a sub-parameter of "y", check your use ofparentheses.

BIMFTRxx-1006 'x' IS NOT A VALID NUMERIC VALUEThe character string "x" was coded where a numeric value is expected, but itis not a valid number. If "x" was not intended to be a number, it may be


Page 444 Messages

positioned incorrectly in relation to other sub-parameters at the same level,or incorrect use of parentheses may have caused it to be associated with thewrong parameter.

BIMFTRxx-1007 'x' EXCEEDS THE ALLOWED NUMBER OF n CHARACTERS/DIGITSFor a non-numeric positional parameter, "x" contains too many characters.For a numeric parameter, "x" is too large a number for the positionalparameter. If "x" is correct as coded, it may be positioned incorrectly inrelation to other sub-parameters at the same level, or the incorrect use ofparentheses may have caused it to be associated with the wrong parameter.

BIMFTRxx-1008 'x' IS NOT A VALID TIME OF DAY VALUEA time of day value of the format "HH:MM:SS.T" was expected where "x"was coded. If "x" is not intended to be a time of day value, it may bepositioned incorrectly in relation to other sub-parameters at the same level,or incorrect use of parentheses may have caused it to be associated with thewrong parameter.

BIMFTRxx-1009 DELIMITER 'x' IS INVALID FOLLOWING 'y', AND IS IGNOREDThe delimiter "x" was coded where it is not allowed. A "/" delimiter isallowed only after certain parameters, and a "(" cannot immediately followanother delimiter.

BIMFTRxx-1010 EXTRA RIGHT PARENTHESES FOLLOWING 'x' IGNOREDMore right parentheses ")" have been found than are needed. Either a leftparenthesis "(" is missing, or too many right parentheses were coded.

BIMFTRxx-1011 MISSING n RIGHT PARENTHESES AT END OF COMMANDThe end of command has been reached, but "n" left parentheses "(" have notbeen paired with right parentheses ")". Either a continuation character ismissing (the next line will start a new command), or too few rightparentheses ")" were coded.

BIMFTRxx-1012 COMMENT IS NOT TERMINATED WITH '*/', OR CONTINUATION IS MISSING ONTHIS LINEA comment was started with "/*" but was not terminated properly.Comments follow the same continuation rules as parameters, and must beterminated by "*/".

BIMFTRxx-1013 STRING 'x' IS NOT TERMINATED WITH A QUOTE, OR CONTINUATION ISMISSING ON THIS LINEThe character string "x" was started as a quoted string, but an ending quote(') was not found.

BIMFTRxx-1014 STRING 'x' IS NOT FOLLOWED BY A SEPARATOR CHARACTER, OR ONE QUOTEWAS CODED WHERE TWO ARE REQUIREDThe character string "x" was started as a quoted string, and another quote (')was found which was not followed by a separator character (to end thestring).


Messages Page 445

BIMFTRxx-1015 END OF INPUT REACHED - LAST INPUT LINE CANNOT BE CONTINUEDThe last line in the SYSIN file ended with a continuation character. Sincethere are no more lines to process, continuation is invalid. If you did notintend the SYSIN file to end at this point, check your input for "/*" appearingin the first position of a SYSIN line. This is treated as end-of-file, not the startof a comment.

BIMFTRxx-1016 COMMAND NOT PROCESSED DUE TO SYNTAX ERRORS - CONDITION CODE nThe condition code set by previous errors for this command exceeds themaximum allowed. The highest condition code for all errors for thiscommand is "n".

BIMFTRxx-1017 'x' IS NOT A VALID JULIAN DATE VALUEA julian date value in the format "YY/DDD" was expected where "x" wascoded. If "x" is not intended to be a julian date value, it may be positionedincorrectly in relation to other sub-parameters at the same level, or incorrectuse of parentheses may have caused it to be associated with the wrongparameter.

BIMFTRxx-1096 PATCH HEX STRING CONTAINS ODD NUMBER OF DIGITSThe internal debugging facility has been invoked to patch a module. Ahexadecimal verify or replace string was coded which does not represent awhole number of bytes. For example, X'47F0' is valid; x'47F' is not valid.

BIMFTRxx-1097 PATCH VERIFY ERRORThe internal debugging facility has been invoked to patch a module, but thedata being verified does not match what is in the module.

BIMFTRxx-1098 INTERNAL ERROR - CANNOT FIND TYPE=FINALAn internal logic error has occurred. Request assistance from a supportrepresentative.

BIMFTRxx-1099 INTERNAL ERROR - CANNOT FIND TYPE=SEG FOR xxxxxxxxAn internal logic error has occurred. Request assistance from a supportrepresentative.

BIMFTRxx-1100 (module+offset) INTERNAL ERROR - INVALID MESSAGE NUMBERX'xxxxxxxx'(n)An internal program error has occurred at the location indicated by themodule and offset information. The module has attempted to issue an errornumber which is not in any message tables. When requesting technicalassistance for this error, please state the full error message.

BIMFTRxx-1101 (module+offset) function/macro INTERNAL ERROR - RETURN CODEX'xxxxxxxx'(n)An internal program function has issued an operating system macro whichfailed. The function was called at the location indicated by the module andoffset information. When requesting technical assistance for this error, pleasestate the full error message.


Page 446 Messages

BIMFTRxx-1102 (module+offset) function/macro INTERNAL ERROR - RETURN CODEX'xxxxxxxx'(n) WHILE ISSUING MESSAGE mmmmWhile attempting to issue message number "mmmm", an internal programfunction issued an operating system macro which failed. The function wascalled at the location indicated by the module and offset information. Alsorefer to message "BIMFTRxx-mmmm" which may help you determine thecause of the problem. When requesting technical assistance for this error,please state the full error message.

BIMFTRxx-1103 GETMAIN(GM) / FREEMAIN(FM) STATISTICSGMCOUNT=n GMTOT=nFMCOUNT=n FMTOT=nCURRENT=n MAXIMUM=nLARGEST SINGLE GETMAIN=nAn internal debugging function has requested a display of the memorystatistics.

BIMFTRxx-1104 (module+offset) function/macro PROGRAM 'xxxxxxxx' NOT FOUNDBIMFTRxx attempted to load program "xxxxxxxx", but it was not found inthe Load Libraries available in the job step. The load function was called atthe location indicated by the module and offset information. This message isissued only if the program cannot be found; other load errors will producemessage BIMFTRxx-1105 or BIMFTRxx-1108

BIMFTRxx-1105 function/macro REQUEST FOR n BYTES OF MAIN STORAGE FAILED. USE A LARGERREGION PARAMETERThe indicated internal function issued an operating system macro whichrequired more main storage than was available. If the number of bytesneeded is not known, the message will say "REQUEST FOR MAINSTORAGE FAILED". Execute BIMFTRxx with a larger region parameter. Ifthe problem persists, determine the cause of excessive main storage use.

BIMFTRxx-1105 function/macro REQUEST FOR n BYTES OF MAIN STORAGE FAILED. USE A LARGERPARTITION, OR A SMALLER SIZE PARAMETERThe indicated internal function issued an operating system macro whichrequired more main storage than was available. If the number of bytesneeded is not known, the message will say "REQUEST FOR MAINSTORAGE FAILED." Execute DTA$$$$ in a larger partition (or use a smallerSIZE= parameter). If the problem persists, determine the cause of excessivemain storage use.

BIMFTRxx-1106 (module+offset) function/macro INVALID PRINT FILE 'filename'BIMFTRxx was unable to open "filename" as a printer file. Check your JCLand parameters. If you request technical assistance for this error, please statethe full error message.

BIMFTRxx-1107 CANNOT LOAD SORT - ADD AT LEAST nK TO EXEC SIZEBIMFTRxx attempted to load the SORT program into the partition, but theSIZE= parameter on the EXEC JCL statement is too small. The SIZE


Messages Page 447

parameter must allow enough room for BIMFTRxx, plus at least 64K forSORT.

BIMFTRxx-1108 (module+offset) function/macro INTERNAL ERROR - ABEND CODE X'xxxx',REASON CODE X'xxxx'An internal program function has issued an operating system macro whichfailed. The function was called at the location indicated by the module andoffset information. The system abend code and reason code are displayed.When requesting technical assistance for this error, please state the full errormessage.

BIMFTRxx-1150 (module+offset) xxxxxxxx FUNCTION HAS BEEN ENTEREDThe operating system interface module has been called from (module+offset)to perform a "xxxxxxxx" function. This message is issued only if the internaltrace has been turned on.

BIMFTRxx-2201 CDLOAD ERROR ON BIMXPC00BIMFTRxx uses the POWER XPCC interface. As part of this interface,BIMFTRxx requires access to module BIMXPC00 which contains the requiredXPCC control blocks. Module BIMXPC00 was provided on the ProductInstallation Tape. Make sure it is in a library accessible to BIMFTRxx.

BIMFTRxx-2202 IDENTIFY FAILURE, RC=xxVSE rejected the attempt by BIMFTRxx to identify itself to the POWER XPCCinterface. Refer to the section “VSE XPCC Response Codes” on page 456.

BIMFTRxx-2203 VSE/POWER BEING TERMINATEDThe VSE XPCC interface has notified BIMFTRxx that POWER is beingterminated.

BIMFTRxx-2204 CONNECT FAILURE, RC=xxVSE rejected the attempt by BIMFTRxx to connect itself to the POWER XPCCinterface. Refer to the section “VSE XPCC Response Codes” on page 456.

BIMFTRxx-2205 CONNECT NOT COMPLETED IN 2 MINUTESPOWER did not respond to the connection request from BIMFTRxx within a2 minute timer. Request technical assistance for this problem.

BIMFTRxx-2206 DISCONNECT FAILURE, RC=xxVSE rejected the attempt by BIMFTRxx to disconnect itself from the POWERXPCC interface. Refer to the section “VSE XPCC Response Codes” on page456.

BIMFTRxx-2207 TERMINATE FAILURE, RC=xxVSE rejected the attempt by BIMFTRxx to terminate the POWER XPCCinterface. Refer to the section “VSE XPCC Response Codes” on page 456.


Page 448 Messages

BIMFTRxx-2208 VSE/POWER TERMINATED ABNORMALLYThe VSE XPCC interface has notified BIMFTRxx that POWER has terminatedabnormally.

BIMFTRxx-2209 SENDR FAILURE, VSE RC/REAS=rc/re,POWER RC/FDBK=rc/fbA failure occurred while BIMFTRxx was attempting to send data to POWERvia the XPCC interface. If the VSE return code/reason code is non-zero, thenVSE rejected the request. If the POWER return code/feedback are non-zero,then POWER rejected the request. Refer to the sections “VSE XPCC ResponseCodes” on page 456 and “POWER XPCC Response Codes” on page 457.

BIMFTRxx-2210

PUT

PUT-EOFPUT-QUITCOMMAND

FAILURE AT

OPEN

SDATASENDR

,

POWER RC/FDBK=rc/fbA failure occurred while BIMFTRxx was attempting to use the POWERXPCC interface. Refer to the section “POWER XPCC Response Codes” onpage 457.

BIMFTRxx-2211 INPUT LINE LONGER THAN SEND-BUFFER, xxxx/yyyyBIMFTRxx attempted to send a single line of data to POWER that was longerthan the maximum expected. 'xxxx' is the line length in Hex, yyyy is themaximum expected in Hex.

BIMFTRxx-2212 INSUFFICIENT GETVIS IN POWER PARTITIONBIMFTRxx could not activate the current XPCC link to POWER without thepossibility of POWER running out of GETVIS. Try the request again later. Ifthe problem persists, consider increasing the GETVIS size in you POWERpartition. Each XPCC link requires a minimum of 3K of GETVIS in thePOWER partition, plus space for a POWER data buffer.

BIMFTRxx-2299 INVALID PARM AREA - xxxxxxxxAn internal error occurred attempting to pass data to module BIMXCPMD.Request technical assistance for this problem.

BIMFTRxx-2501 CDLOAD ERROR ON BIMXMC00BIMFTRxx requires access to module BIMXMC00 which contains therequired XPCC control blocks for Cross-Partition Communication. ModuleBIMXMC00 was provided on the Product Installation Tape. Make sure it is ina library accessible to BIMFTRxx.

BIMFTRxx-2502 IDENTIFY FAILURE, IDENT=xxxxxxxx, RC=xxVSE rejected the attempt by BIMFTRxx to identify itself to the XPCC interfaceas 'xxxxxxxx'. Refer to the section “VSE XPCC Response Codes” on page 456.


Messages Page 449

BIMFTRxx-2503 REQUESTED APPLICATION-xxxxxxxx IS NOT ACTIVEBIMFTRxx cannot communicate to Application 'xxxxxxxx' because theApplication is not active in your VSE System.

BIMFTRxx-2504 CONNECTION TO xxxxxxxx IS BUSYRequest technical assistance for this problem.

BIMFTRxx-2505 CONNECTION TO xxxxxxxx NOT COMPLETED IN 2 MINUTESApplication 'xxxxxxxx' did not respond to the connection request fromBIMFTRxx within a 2 minute timer. Request technical assistance for thisproblem.

BIMFTRxx-2506 DISCONNECT FAILURE, RC=xxVSE rejected the attempt by BIMFTRxx to disconnect itself from the XPCCinterface. Refer to the section “VSE XPCC Response Codes” on page 456.

BIMFTRxx-2507 TERMINATE FAILURE, RC=xxVSE rejected the attempt by BIMFTRxx to terminate the XPCC interface.Refer to the section “VSE XPCC Response Codes” on page 456.

BIMFTRxx-2508 CONNECTION TO xxxxxxxx TERMINATED ABNORMALLYThe VSE XPCC interface has notified BIMFTRxx that Application 'xxxxxxxx'has terminated abnormally.

BIMFTRxx-2509 xxxxxxxx FAILURE, VSE RC/REAS=rc/reA failure occurred while BIMFTRxx was attempting XPCC function'xxxxxxxx'. Refer to the section “VSE XPCC Response Codes” on page 456.

BIMFTRxx-2510 RECEIVE FROM xxxxxxxx NOT COMPLETED IN 2 MINUTESApplication 'xxxxxxxx' did not respond to the receive request fromBIMFTRxx within a 2 minute timer. Request technical assistance for thisproblem.

BIMFTRxx-2511 CONNECTION TO xxxxxxxx TERMINATED NORMALLYRequest technical assistance for this problem.

BIMFTRxx-2512 XMCFPOST DETECTEDRequest technical assistance for this problem.

BIMFTRxx-2599 INVALID PARM AREA - xxxxxxxxAn internal error occurred attempting to pass data to module BIMXMCMD.Request technical assistance for this problem.

BIMFTRxx-2850 INVALID FUNC REQUEST RCVD <xxxxxxxx>A request for APPC services was received from the host application that wasinconsistent with the state of the existing conversation. This can occur if thePC has terminated abnormally without notifying the host. This message isdisplayed on SYSLOG and the CICS CSMT destination.


Page 450 Messages

BIMFTRxx-2851 STORAGE MGMT ERROR: FUNC(xxxx), RC(nnnn)A CICS GETMAIN or FREEMAIN error has been detected by the APPC API.This message is displayed on SYSLOG and the CICS CSMT destination.

BIMFTRxx-2854 FUNC(xxxx) FAILED, RC(rrrr)APPC action request xxxx has failed. The reason is explained in 'rrrr'. AnyLU6.2 communications request may be identified in the xxxx field. Usuallythis message occurs because the communications session has beenabnormally terminated or interrupted. This message is displayed on SYSLOGand the CICS CSMT destination.

BIMFTRxx-2855 (descriptive text)This is a general error message designed to carry a message from anotherphase of the APPC API. This message is displayed on SYSLOG and the CICSCSMT destination.

BIMFTRxx-2860 INVALID LOGICAL RECORD FND - ISSUE ERROR SENTAn incoming message block did not contain the requisite APPC basicconversation block header bytes. The API has signaled the PC that theincoming data is incorrect. This message is displayed on SYSLOG and theCICS CSMT destination.

BIMFTRxx-2861 VTAM-LU62 ERROR CODE xxxxxxxxxxxxAn APPC error condition was delivered to the APPC API indicating that theconversation is in trouble. The xxxxx provides a generalized interpretation ofthe condition if the return code is commonly known. This message isdisplayed on SYSLOG and the CICS CSMT destination.

BIMFTRxx-2863 INVALID SEND OPTION FOUND (xxxx)The APPC API has detected an invalid LU6.2 conversation “SEND” verboperand. This may be caused by an invalid request submitted by the hostapplication or a corrupted request block. The request is rejected and the APIreturns to the host application. This message is displayed on SYSLOG andthe CICS CSMT destination.

BIMFTRxx-3000 (fromappl)

OPEN

CLOSE COMPLETED

Informational message to indicate that the VTAM ACB for (fromappl) hasbeen either opened or closed successfully.

BIMFTRxx-3001 (fromappl) CONNECTION ESTABLISHED WITH toapplInformational message to indicate that an APPC connection has beenestablished between (fromappl) and toappl.

BIMFTRxx-3002 (fromappl) CONNECTION TERMINATED WITH toapplInformational message to indicate that an APPC connection has beenterminated between (fromappl) and toappl.


Messages Page 451

BIMFTRxx-3003 (fromappl) VTAM OPEN FAILED, R15=nnnnnnnn, EC=xx,REASON=(descriptive text), nnn WAITS OCCURREDThis message is generated if the VTAM open for (fromappl) fails. TheREASON field provides a descriptive text description of the VTAMACBERFLG (EC). Processing is terminated with a job/step condition code of12.

BIMFTRxx-3004 (fromappl) NO ALLOCATED SESSION, FUNCTION=(function name)TERMINATEDRequest technical assistance for this error.

BIMFTRxx-3005 (fromappl) THE FOLLOWING APPCCMD FUNCTION HAS FAILED:(VTAM appc function name)FUNCTION=(bimapcmd function name)RPLFDBK=xxxxxxxx, RPLREASON=(descriptive text)RPL6RC=xxxxxxxx, RPL6REASON=(descriptive text)STATE=xxxxxxxx, RPL6RLEN=nnnnnIf the descriptive text and VTAM return codes do not provide a solution toyou, then request technical assistance for this error.

BIMFTRxx-3006 (fromappl) REQUESTED APPLICATION (toappl) IS NOT AVAILABLE,RPLFDBK=nnnnnnnn, RPLREASON=(descriptive text)BIM-PC/TRANSFER could not establish an APPC connection to (toappl). Ifthe descriptive text and VTAM feedback do not provide a solution to you,then request technical assistance for this error.


Page 452 Messages

Allocation / Deallocation ErrorsThe following messages can occur during dynamic allocation and/ordeallocation of datasets within BIM-PC/TRANSFER:

VSE Messages:

2001 ALLOCATE REQUEST FAILED, FUNC=xxxxxxxx,RC=xxRequest technical assistance for this message.

2002 DE-ALLOC REQUEST FAILED, FUNC=xxxxxxxx,RC=xxRequest technical assistance for this message.

2003 DLBL FILENAME-xxxxxxxx FOUND IN JCLThe requested VSAM Cluster could not be allocated because a DLBL alreadyexists.

2004 DLBL FILENAME-xxxxxxxx NOT FOUND IN JCLThe requested VSAM Cluster could not be de-allocated because its DLBLcould not be found.

MVS Messages:

If you are running MVS/ESA, one or more narrative text messages will begenerated describing the exact reason for the error. For pre-MVS/ESA systems,one of the following messages will be generated:

020C - Exclusive use not honored0210 - Dataset not Available0220 - Volume not Available

BIM-PC/TRANSFER could not gain exclusive use of a dataset for uploading.

0394 - Status and Rel GDG no CompatibleYou have requested an upload to a new GDG dataset with a relative numberthat has already been used in the current execution of CICS or BIM-TMAN.MVS does not reset relative GDG numbers until the end of job, which in thiscase is when CICS or BIM-TMAN is cycled.

1708 - Dataset not FoundThe requested dataset is not currently cataloged.

2001 ALLOCATE REQUEST FAILED, RC=xx, EC=xxxx, IRC=xxxx,ERSN=xxxxxxxx

This error occurs if a dynamic allocation request is rejected by MVS.


Messages Page 453

RC is the “Return Code”, it indicates the type of error:

04 - An error resulted from the current environment, theunavailability of a system resource, or a system routine failure;there will also be an error reason code.

08 - The installation validation routine denied this request.0C - The error is due to an invalid parameter list; there will also be

an error reason code.

EC is the “Error Reason Code”, it explains the reason for the return code.The following table contains a partial list of error reason codes, acomplete list can be found in the MVS or MVS/XA System Macros andFacilities manual 'GC28-1150' or for MVS/ESA in manual GC28-1645,Application Development Guide: Authorized Assembler LanguagePrograms.

CLASS 2 CODES (UNAVAILABLE SYSTEM RESOURCE)

0204 Real storage unavailable.020C Request for exclusive use of a shared data set cannot be honored.0210 Requested data set unavailable.0214 Unit(s) not available.0218 Specified volume or an acceptable volume is not mounted.021C Unit name specified is undefined.0220 Requested volume not available.0224 Eligible device types do not contain enough units.0228 Specified volume or unit in use by system.022C Volume mounted on ineligible permanently resident or reserved unit.0230 Permanently resident or reserved volume on required unit.0240 Requested device is a console.0260 Unit does not meet specified status requirements.0264 Invalid request due to current unit status.0268 Tape device is broken.

CLASS 3 CODES (INVALID PARAMETER LIST)

0340 Dsname not specified and disposition not “new”.035C Invalid PARM specified in text unit.10364 JOBLIB/STEPLIB/JOBCAT/STEPCAT specified as ddname.0368 Authorized function requested by unauthorized user.0380 Mutually exclusive KEY specified.10384 Mutually inclusive KEY specified.10388 Required KEY not specified.0390 GDG specified with relative generation number exceeds 35 chars.0394 Status and relative generation number are incompatible.039C Device type and volume are incompatible.

CLASS 4 CODES (ENVIRONMENTAL ERROR)

0410 Specified ddname unavailable.0420 Specified ddname or dsname associated with an open data set.0440 Specified dsname not found.0448 Request for a new data set failed; data set already exists.044C Request was made for a data set that has a disposition of delete.0458 Dsname in DCB reference is a GDG group name.0484 Request denied by operator.0488 GDG Pattern DSCB not mounted.048C GDG Pattern DSCB not found.

CLASS 17 CODES (SYSTEM ROUTINE ERRORS)

1708 Dataset not found.

1 The Information Reason Code contains the value of the key that caused the error.


Page 454 Messages

IRC is the “Information Reason Code”, it further explains the reason for thereturn code. The contents of this field will vary depending on the ErrorReturn Code. The primary contents of this field will be the value of the“KEY” that caused the error. The following table contains a list of theKEY fields used:

0001 Ddname0002 Data Set Dsname0003 GDG / Member name0004 Data Set Status0005 Data Set Normal Disposition0006 Data Set Conditional/Abnormal Disposition0007 Track Space Type0008 Cylinder Space Type0009 Block length (Space allocation)000A Primary Space Quantity000B Secondary Space Quantity000D Unused Space Release (RLSE)0010 Volume Serial number (VOLSER)0015 Unit Description (UNIT)0018 SYSOUT Class0019 SYSOUT Program Name001C Unallocation at Close (FREE)001E Label Type001F Label Sequence Number0022 Expiration Date (EXPDT)0023 Retention Period (RETPD)002C DCB=dsname0030 DCB=BLKSIZE0042 DCB=LRECL0049 DCB=RECFM0055 Returned DDNAME0056 Returned DSNAME0057 Returned DSORG8004 SMS Storage Class8005 SMS Management Class8006 SMS Data Class

ERSN is the SMS Reason Code.

2002 DE-ALLOC REQUEST FAILED, RC=xx, EC=xxxx, IRC=xxxx,ERSN=xxxxxxxx

This error occurs if a dynamic de-allocation request is rejected by MVS. Referto message 2001 for a description of RC, EC and IRC.


Messages Page 455

EIBRESP CodesSeveral of the messages generated by BIM-PC/TRANSFER contain an EIBRESPcode from CICS or BIM-TMAN. The following table provides a list of thosecodes. The table has been copied from the CICS Application ProgrammingReference manual (SC33-0713).

00 NORMAL

01 ERROR02 RDATT03 WRBRK04 EOF05 EODS06 EOC07 INBFMH08 ENDINPT09 NONVAL

10 NOSTART11 TERMIDERR12 FILENOTFOUND13 NOTFND14 DUPREC15 DUPKEY16 INVREQ17 IOERR18 NOSPACE19 NOTOPEN

20 ENDFILE21 ILLOGIC22 LENGERR23 QZERO24 SIGNAL25 QBUSY26 ITEMERR27 PGMIDERR

28 TRANSIDERR29 ENDDATA

30 INVTSREQ31 EXPIRED32 RETPAGE33 RTEFAIL34 RTESOME35 TSIOERR36 MAPFAIL37 INVERRTERM38 INVMPSZ39 IGREQID

40 OVERFLOW41 INVLDC42 NOSTG43 JIDERR44 QIDERR45 NOJBUFSP46 DSSTAT47 SELNERR48 FUNCERR49 UNEXPIN

50 NOPASSBKRD51 NOPASSBKWR53 SYSIDERR54 ISCINVREQ55 ENQBUSY56 ENVDEFERR

57 IGREQCD58 SESSIONERR59 SUSBUSY

60 SESSBUSY61 NOTALLOC62 CBIDERR63 INVEXITREQ64 INVPARTNSET65 INVPARTN66 PARTNFAIL

70 NOTAUTH72 SUPPRESSED73 WRONGSTAT74 NAMEERROR76 CCERROR77 MAPERROR

80 NOSPOOL81 TERMERR82 ROLLEDBACK83 END84 DISABLED87 OPENERR

91 TASKIDERR92 TCIDERR94 LOADING


Page 456 Messages

VSE XPCC Response CodesSeveral of the messages generated by BIM-PC/TRANSFER contain a return code(RC) and/or a reason code (REAS) from VSE. The following tables define themeanings of those codes.

Return Codes (RC)03 MORE CONNECT REQUESTS FOR THIS SUBSYSTEM PENDING04 OTHER SIDE DID NOT IDENT UNTIL NOW05 OTHER SIDE DID NOT CONNECT UNTIL NOW06 XPCCB CONTROL-BLOCK FORMAT ERROR07 WRONG IDENTIFY TOKEN08 WRONG PATH ID TOKEN09 REQUEST WAS DONE FROM A TASK WITH DIFFERANT TASK-ID0A INVALID BUFFER LIST (INDICATOR WRONG)0B TOO MANY BUFFERS OR BUFFER LENGTH more than 16 MEG0C RECEIVING BUFFER TOO SMALL0D TOO MANY CONNECT'S FOR A USER APPL0E REQUEST NOT POSSIBLE BECAUSE NO SYSTEM STORAGE AVAILABLE0F AT LEAST ONE PARTNER OF A CONNECTION MUST BE A SUBSYSTEM10 NO REQUEST PENDING11 REQUEST WAS CLEARED12 LINE ALREADY BUSY13 REPLY CMD WAS ISSUED BEFORE DATA RECEIVED14 CONNECTIONS STILL BUSY FOR APPL15 BUSY FROM OWN SEND16 SEND FROM OTHER SIDE PENDING17 OTHER SIDE ISSUED TERMQSCE18 A CONNECTION WAS NEVER EXISTING19 THE OTHER SIDE TERMINATED NORMALLY1A THE OTHER SIDE TERMINATED ABNORMALLY1B REQUEST ALREADY CLEARED1C XPCCB ADDR OF THIS REQ IS DIFFERENT FROM CONNECT

Reason codes (REAS)

01 AFTER SEND/SENDR THE RECEIVER ISSUED PURGE02 SENDER ISSUED CLEAR BEFORE RECEIVER WAS ABLE TO RECEIVE/REPLY03 AFTER SENDR CMD WHEN THE RECEIVE IS EXECUTED BY PARTNER05 OTHER SIDE TERMINATED DURING CONNECTThe following bits are or’ed with the above bits.40 OTHER SIDE ISSUED DISCONNECT80 OTHER SIDE WAS DISCONNECTED DUE TO ABNORMAL TERMINATION


Messages Page 457

POWER XPCC Response CodesSeveral of the messages generated by BIM-PC/TRANSFER contain a return code(RC) and a feedback code (FDBK) from POWER. The following table defines themeanings of those codes.

RC/FDBK04/01 JOB/OUTPUT NOT FOUND04/02 JOB/OUTPUT PROTECTED04/03 JOB/OUTPUT MARKED ACTIVE (BUSY)04/08 SHORT ON SPOOL FILE SPACE (SOD)04/09 SHORT ON ACCOUNT FILE SPACE (SOA)04/0A REQUEST PROHIBITED IN BROWSE MODE04/0B NOTHING FOUND IN QUEUE(S) (DISPL)04/0D NO MATCHING USER ID08/01 INVALID SPL08/05 INVALID JOB NAME08/06 INVALID QUEUE IDENTIFIER08/07 INVALID CLASS08/08 INVALID PASSWORD08/09 INVALID USER/REMOTE-ID08/0A INVALID RECORD FORMAT08/0B INVALID DISPOSITION08/0C INVALID PRIORITY08/0D INVALID SYTEM IDENTIFIER08/0E INVALID DESTINATION NODE08/0F INVALID DEST. USER/REMOTE08/10 INVALID FORMS IDENTIFIER08/11 INVALID FCB NAME08/1A BUFFER TOO SMALL08/1E INVALID PROGRAMMER NAME08/1F INVALID ROOM NUMBER08/20 INVALID DEPARTMENT NUMBER08/21 INVALID BUILDING NUMBER08/22 CONFLICTING SPECIFICATIONS08/23 RECEIVED RECORD TOO LARGE08/24 INVALID BUFFER TYPE08/25 REQUEST OUT OF SEQUENCE08/26 SPL RECEIVED OUT OF SEQUENCE08/27 RECEIVED BUFFER OUT OF SEQUENCE08/28 REQUEST PROHIBITED08/29 INVALID SIGNAL SPECIFICATION08/31 INVALID JOB NUMBER(=0)08/32 INVALID JOB SUFFIX NO (>127)08/33 INVALID USER INFORMATION08/35 UNEXPECTED RESPONSE RECEIVED08/46 INVALID SECURITY USERID08/47 INVALID SECURITY PASSWD08/48 INVALID PROCESSING MODE0C/01 SEND ISSUED/ BUT SENDR REQUIRED0C/03 BUFFER TOO LARGE10/03 CONNECTION ALREADY ACTIVE10/06 SEVERE INTERNAL ERROR


Page 458 Messages


Page 459

APPENDIX A


Page 460 APPENDIX A


APPENDIX A (How to Code Commands) Page 461

How To Code Commands (Syntax)This section describes the rules for coding BIMFTRPR and BIMFTRBCCommands and their Operands. The meaning and use of the Commandsthemselves are not described here. The examples given here are intended only toclarify the coding syntax, not to show how to use a particular Command orOperand.

Commands are coded as one or more lines in a SYSIN dataset. Each Commandmay be continued using any number of lines.

A Command may contain comments, which can be coded anywhere within theCommand. Comments may also be coded separately, rather than as part of aCommand.

Terminology

The special terms defined below are used to describe the Command syntax.

• COMMAND: A Command is a BIM-PC/TRANSFER-defined Commandname followed by Operands and comments. Each Command is defined andprocessed by BIM-PC/TRANSFER as a single entity, and may or may not berelated to other Commands.

• KEYWORD Operand: Keyword Operands are represented in Commanddescriptions with upper-case letters, and indicate BIM-PC/TRANSFER-defined words which either identify sub-Operands that follow the keywordin parentheses, or modify the action taken during the processing of aCommand.

• POSITIONAL Operand: Positional Operands are represented in Commanddescriptions with lower-case letters, and indicate user-provided data neededby the Command.

• SEPARATOR CHARACTER: A separator character is used to end anOperand, and to indicate the relationship of that Operand to other Operands.The separator characters are: space, comma, left and right parentheses, slash,and semi-colon.

• COMMENTS: BIM-PC/TRANSFER allows you to code comments in theSYSIN dataset. Comments are for your own documentation and are printed,but not processed, with the Commands.

Coding Operands

Commands all have this general structure:

COMMAND-NAME Operands ... ;


Page 462 (How to Code Commands) APPENDIX A

The semi-colon (;) is optional, and signals the end of the Command. Anythingcoded after a semi-colon is ignored. The Command-name must be the first wordin a Command, terminated by a space. It is normally followed by Operandswhich further define the action to be taken by the Command. The Operandswhich are allowed after the Command-name are separated using one or morespaces. If an Operand requires one or more sub-Operands, the sub-Operands arecoded in parentheses in this manner:

COMMAND PARM-1 PARM-2(SUB-A(...) SUB-B) PARM-3...

where PARM-1, PARM-2, SUB-A, SUB-B, and PARM-3 are valid keyword orpositional Operands defined for the Command named "COMMAND". OnlyOperands defined as valid for PARM-2 may be coded as sub-Operands followingPARM-2. The Operands PARM-1, PARM-2, and PARM-3 are considered to be atthe same logical level, regardless of any sub-Operands specified for each of them.Operands and sub-Operands of all logical levels follow the same coding rules.

The Command-name, Operands, and separator characters may be preceded orfollowed by any number of spaces. This can be used to make Commands morereadable, and easier to maintain.

Keyword Operands can be coded in any order, unless the description of aCommand states otherwise. Some keywords may be defined as having one ormore prefixes which alter the meaning of the keyword.

Positional Operands may be coded in a variety of ways, to allow you to specifyany type of data. If the data needed for an Operand contains separator charactersor non-printable characters, code the Operand as a quoted string or as ahexadecimal string. If an Operand is defined as a number, you may code it eitheras a decimal number, or use hexadecimal notation. The relative position of eachpositional Operand within the Command determines the sequence in which theyare acted upon.

Coding Continuation

You may specify any Command on more than one input line by coding either a"+" or "-" as the last non-blank character of all but the last line of the Command.If a "-" is used as the continuation character, the Command is continued startingat the left margin of the following line. If a "+" is used, the Command iscontinued starting with the first non-blank character of the following line. Alldata on the line up to, but not including, the "+" or "-" is used.


APPENDIX A (How to Code Commands) Page 463

The following examples will all have the same result:

COMMAND PARM-1 PARM-2(SUB-A(DATA) SUB-B) PARM-3

COMMAND PARM-1 PARM-2(SUB-A(DA+ TA) SUB-B) PARM-3

COMMAND PARM-1 PARM-2(SUB-A(DA-TA) SUB-B) PARM-3

COMMAND PARM-1 - PARM-2( - SUB-A(DATA) - SUB-B - ) - PARM-3

Continuation works in the same way regardless of whether it takes place in themiddle of a word, within a quoted string or comment, between Operands, orafter a semi-colon (;). It takes place as the lines are read, before any othercharacters are interpreted.

Coding Quoted Strings

Quoted strings are valid for any positional Operand, to allow you to:

• Code data that contains separator characters - 'NOT FOUND'• Code data that would otherwise be interpreted as a keyword.• Code data in hexadecimal notation - x'C8C5E7'• Code lower-case data - 'This will remain lower case'

To specify the quote character within a quoted string, code two consecutivequotes:

'THIS STRING CONTAINS ''QUOTES'' IN IT'

Coding Date Operands

Some Operands require a date to be coded. The format can be either YYDDD,YY/DDD or YY/MM/DD, where YY is the year, MM is the month, DD is the daywithin the month, and DDD is the Julian day number (January 1 = 001, February1 = 032, etc.). You must code exactly three digits for DDD and exactly two digitsfor both the MM and DD values.

You may specify a date that is relative to the current date by coding a "+" or "-" asthe first character of the Julian date. The number of years (optional) and days arethen added to or subtracted from the current system date. When you code arelative date, the number of days can be any number up to 999.

Coding Time Operands

Some Operands require a time of day value to be coded. The format isHH:MM:SS.T, where HH is the hour, MM is the minutes, SS is the seconds, and T


Page 464 (How to Code Commands) APPENDIX A

is the tenths of seconds. The seconds and tenths of seconds are optional, soHH:MM or HH:MM:SS are also valid formats. If you code it without punctuation(HHMMSST), you must specify all seven digits.

Coding Comments

It is often useful to put comments with the Operands. Since a semi-colon ";" endsthe parameter processing of a Command, anything coded after a semi-colon istreated as a comment. If continuation is specified after a semi-colon, the commentis continued to the next line.

A more flexible method of coding comments is provided. A comment mayappear at any point that a separator character is valid, by coding "/* comment*/". Any characters may appear between the "/*" and "*/", and the comment maybe continued to any number of lines by using the normal continuation method. Ifyou do not end the comment, or code a continuation character on the line, anerror message is issued. In the following examples, the lower case charactersrepresent data that are treated as comments:

COMMAND PARM-1;parm-2(sub-a(data) sub-b) parm-3

COMMAND PARM-1 /* comment for parm-1 */ - PARM-2( /* comment for parm-2 */ - /* more comments */ - SUB-A(DATA) - ) - /* a single comment can be- continued */

Index

BIM-PC/TRANSFER Page 465

- (continuation).............................................462

#

#ATLogon/Logoff Scripts...............................70

#BYELogon/Logoff Scripts...............................71

#COPYBIMAFT Scripts.......................................142

#CRLFFile Conversion Scripts ..........................290

#DEFINENAMEBIMAFT Scripts.......................................148

#DOWNLOADBIMAFT Scripts.......................................135

#ENDBIMAFT Scripts.......................................154File Conversion Scripts ..........................293File Upload Scripts .................................184IDCAMS Definitions ..............................322

#ENDIFBIMAFT Scripts.......................................133

#ERASEBIMAFT Scripts.......................................142

#ERRORFile Conversion Scripts ..........................286

#EXECBIMAFT Scripts.......................................141

#GOTOBIMAFT Scripts.......................................153File Conversion Scripts ..........................285File Upload Scripts .................................182

#GROUPBEGFile Conversion Scripts ..........................287

#GROUPENDFile Conversion Scripts ..........................287

#HOSTAFTBIMAFT Scripts.......................................143

#IDCAMSIDCAMS Definitions ..............................322

#IFBIMAFT Scripts.......................................152File Conversion Scripts ..........................283File Upload Scripts .................................180

#IFEXISTSBIMAFT Scripts.......................................133

#IFNOTEXISTSBIMAFT Scripts.......................................133

#INCLUDE

File Upload Scripts..................................181#INSERT

File Conversion Scripts...........................291#KEEP

HOSTAFT Script .............................127, 160#KEEP

HOSTAFT Status Detail Screen.............245#LINE

File Conversion Scripts...........................292#LOOK

Logon/Logoff Scripts ...............................69#MAXCC=

IDCAMS Definitions...............................323#MOVE

BIMAFT Scripts.......................................142#NRECS=

IDCAMS Definitions...............................323#OPTION

BIMAFT Scripts.......................................130LOADNEXT........................................130LOG......................................................130LOGOFF ..............................................131LOGON ...............................................130LOOP ...................................................131PAUSE .................................................131QUIT ....................................................131RELOAD..............................................131RETRY..................................................132START..................................................132STOP ....................................................132

BIMAFT ScriptsPROFILE ......................131File Conversion Scripts...........................273

ASCII....................................................273DECIMALPT.......................................273EOF.......................................................273OUTPUT..............................................273SEPARATOR ......................................273

File Upload Scripts..................................175#PROMPT

BIMAFT Scripts.......................................146File Conversion Scripts...........................280File Upload Scripts..................................177

#RECORDFile Conversion Scripts...........................279

#RECSZ=IDCAMS Definitions...............................323

#RENAMEBIMAFT Scripts.......................................142

#SENDLogon/Logoff Scripts ...............................70

#SENDTO

Index

Page 466 BIM-PC/TRANSFER

HOSTAFT Script ............................ 128, 160#SIGNON

BIMAFT Scripts ...................................... 129#SKIP

File Conversion Scripts.......................... 294#START

BIMAFT Scripts ...................................... 144#TRANSFER

APPEND.................................................. 140ASCII........................................................ 139BIMAFT Scripts ...................................... 139CANCEL ................................................. 140CRLF ........................................................ 139NEW......................................................... 140NODELETE............................................. 139RENAME................................................. 140REPLACE................................................ 140

#UPLOADBIMAFT Scripts ...................................... 137SCRIPT..................................................... 137UNIQUE.................................................. 137

#VOL=IDCAMS Definitions.............................. 323

%

%AVGSZIDCAMS Definitions.............................. 324

%CATDNMIDCAMS Definitions.............................. 324

%CATDSNIDCAMS Definitions.............................. 324

%CLUSTERIDCAMS Definitions.............................. 324

%DLBLIDCAMS Definitions.............................. 324

%NRECSIDCAMS Definitions.............................. 324

%NRECS10IDCAMS Definitions.............................. 325



%RECSZIDCAMS Definitions.............................. 324

%SAMAVGSZIDCAMS Definitions.............................. 325

%SAMMAXSZIDCAMS Definitions.............................. 325

%SAMRECFMIDCAMS Definitions.............................. 325

%VOLIDCAMS Definitions.............................. 324

+

+ (continuation)........................................... 462

1

1472/PC.......................................................... 52

A

Access Security Definitions........................ 223Common Fields

CATGRP ............................................. 228LVL...................................................... 229SECGRP .............................................. 229SEQ...................................................... 229TYPE.................................................... 229

Common Fields:...................................... 228for EDIT ................................................... 231for ICCF ................................................... 234for JES ...................................................... 238for LIBR ................................................... 236for POWER.............................................. 228for Scripts ................................................ 233ForCICS Temporary Storage................. 240Generic Masks ........................................ 224List Screen ............................................... 227LVL........................................................... 223Processing Example ............................... 226Processing Overview ............................. 224Variable Substituion............................... 224

ACCESS SECURITY GROUPCategory Definition Screen ................... 198

Activate Host Transfer Dialog................... 118Activating HOSTAFT Script...................... 163Activating HOSTAFT Script In Batch ...... 163Activating HOSTAFT Script In CICS ....... 172Activity Log

System Options Screen .......................... 192Adding new Definitions............................. 187ALLEVENTS

PRINT Command................................... 263Alternate Maintenance Txn Codes

System Options Screen .......................... 192APPC Connections........................................ 58

Attachmate Personal Client .................... 67BIM-PC/TRANSFER Definitions........... 61CICS Definitions....................................... 60Communications Manager/2 ................. 65DynaComm/Elite..................................... 64IRMA.......................................................... 62

Index


Overview....................................................58PC Configuration ......................................61PC/3270 .....................................................66RUMBA......................................................63VTAM Definitions ....................................59

APPC Emulator..............................................51APPC Settings ................................................50APPEND

#TRANSFER............................................140Category Definition Screen....................197

APPLIDTransfer Activity Log Display...............255

ASCII#OPTION

File Conversion Scripts......................273#TRANSFER............................................139

ASCII FilesFile Conversion Scripts ..........................301

Attachmate Personal Client....................52, 67Auto Settings Dialog ...................................115Automatic Transfer Script ..........................125

B

BIM$BIM$FB0...................................................206BIM$VB0 ..................................................206BIMFTRDC

bim$dn0.......................................320, 321bim$up0.......................................320, 321

BIM-TMAN Considerations ..................206CLUSTER / UCAT .................................208Cluster Name Transfer Feature ............205

bim$dn0 ................................................320, 321BIM$FB0........................................................206bim$up0 ................................................320, 321BIM$VB0.......................................................206BIMAFT

#COPY......................................................142#DEFINENAME .....................................148#DOWNLOAD .......................................135#END........................................................154#ENDIF ....................................................133#ERASE....................................................142#EXEC ......................................................141#GOTO.....................................................153#HOSTAFT..............................................143#IF .............................................................152#IFEXISTS ................................................133#IFNOTEXISTS .......................................133#KEEP ......................................................127#MOVE ....................................................142

#OPTION .................................................130#PROMPT................................................146#RENAME ...............................................142#SENDTO ................................................128#SIGNON.................................................129#START....................................................144#TRANSFER............................................139#UPLOAD................................................137Auto Settings Dialog...............................115Automatic Transfer Script .....................125File Pulldown ..........................................112Help Pulldown ........................................114Labels........................................................151Main Window..........................................111Process Pulldown....................................113Sample Scripts .........................................155Script Recording......................................117Script Syntax............................................126Starting DOS Version .............................109Starting OS/2 Version ............................109Starting Windows 3.1 Version...............108Starting Windows 95/98/NT Version .108

BIMDOSCK ....................................................55BIM-EDIT....................... (See EDIT Transfers)BIM-EPIC....................... (See EDIC Transfers)BIM-EPIC DSN

SAM Profile Screen.................................212BIMFCV

Customizing.............................................270BIMFTRBC

APPL Definitions ....................................164CICS Definitions......................................165Commands and Operands.....................166MVS JCL...................................................166VSE JCL ....................................................166VTAM Definitions...................................164

BIMFTRD$Driver Specifications...............................307

BIMFTRDBDriver Specifications...............................310

BIMFTRDCDriver Specifications...............................315

BIMFTRDDDriver Specifications...............................328

BIMFTRDEDriver Specifications...............................330

BIMFTRDFDriver Specifications...............................337

BIMFTRDIDriver Specifications...............................345

BIMFTRDJ

Index


Driver Specifications.............................. 347BIMFTRDL

Driver Specifications.............................. 351BIMFTRDM

Driver Specifications.............................. 354BIMFTRDP

Driver Specifications.............................. 356BIMFTRDQ

Driver Specifications.............................. 362BIMFTRDR

Driver Specifications.............................. 365BIMFTRDT

Driver Specifications.............................. 368BIMFTRDV

Driver Specifications.............................. 370BIMFTRDX

Driver Specifications.............................. 375BIMFTRPR ................................................... 261

Commands and Operands.................... 262MVS JCL.................................................. 262VSE JCL ................................................... 261

BIMLOGONLogon/Logoff Script Recorder............... 74

BIM-TMANCluster Name Transfer Feature............ 206Setup (MVS).............................................. 37Setup (VSE) ............................................... 25Startup JCL (MVS) ............................. 33, 34Startup JCL (VSE)............................... 21, 22VTAM APPL statement........................... 59

BLKSIZESAM Profile Screen ................................ 213

C

CANCEL#TRANSFER ........................................... 140

CATEGORYCategory Definition Screen................... 195Transfer Activity Log Display.............. 255

Category Definition List............................. 194Category Definition Screen........................ 195

ACCESS SECURITY GROUP ............... 198APPEND.................................................. 197CATEGORY ............................................ 195CRLF ........................................................ 199DEFAULT ............................................... 197DESC........................................................ 197DRIVER ................................................... 198DRIVER DATA....................................... 199EXIT ......................................................... 198Key Fields................................................ 195

LIBQUE.................................................... 196NEW......................................................... 197REPLACE ................................................ 197SECEXIT .................................................. 198SECGRP................................................... 198TRANSLATE .......................................... 199TRTABLE ................................................ 199TYPES ...................................................... 197

CATGRPAccess Security Definitions................... 228

ChecksumUpload Validation.................................... 93

CICS Requirements for MVS....................... 34CICS Requirements for VSE ........................ 23CICS Temporary Storage Access .............. 354CICS Transient Data ................................... 368CLUSTER

VSAM Profile Screen ............................. 208Cluster Name Transfer Feature................. 205CMD

HOSTAFT Status Detail Screen............ 245Script Definitions Screen ....................... 218

CMDPFX=File Upload Scripts................................. 175

Coding Operands........................................ 461COMMAND

Script Definitions Screen ....................... 217Commands

Coding Syntax ........................................ 461CONNECT Command........................... 168Continuation Syntax .............................. 462HOSTAFT Command ............................ 169OPTION Command ............................... 167PRINT Command................................... 263Syntax ...................................................... 262UPARM Command................................ 171

Comments (syntax) ..................................... 464Communications Manager/2 ...................... 65Configurator .................................................. 53CONNECT Command ............................... 168Connection Profiles

#OPTION ................................................ 131Turning On and Off ................................. 93

Connection Settings Dialog.......................... 42ConnectionProfiles

Profile Details Dialog............................... 45Profile List Dialog..................................... 44Settings Dialog.......................................... 43Using in Automatic Transfers................. 46Using in Manual Transfers...................... 46

Continuation Syntax ................................... 462

Index


CONTINUE=File Upload Scripts .................................176

Control File for MVS .....................................32Control File for VSE ......................................21CRLF

#TRANSFER............................................139Category Definition Screen....................199SAM Profile Screen.................................212VSAM Profile Screen..............................207

D

DATASETVSAM Profile Screen..............................205

DATASET ACCESSUser Definition Screen ...........................202VSAM Profile Screen..............................205

Dataset Access List ......................................220Dataset Access Screen .................................221

DATASET NAME MASK......................222DESC.........................................................222Key Fields ................................................221NAME ......................................................221SECGRP....................................................222

DATASET NAME MASKDataset Access Screen ............................222

Date Operands .............................................463DATEFMT=

File Upload Scripts .................................175DECIMALPT

#OPTIONFile Conversion Scripts......................273

DEFAULTCategory Definition Screen....................197

Default LIBQUE values for downloadsDEFAULT ................................................197

Default Security ExitSystem Options Screen...........................191

Default Translate TableSystem Options Screen...........................192

Defining Control File for MVS.....................32Defining Control File for VSE ......................21Defining Log File for MVS ...........................33Defining Log File for VSE.............................22Definitions

Adding .....................................................187Deleting ....................................................188Replacing .................................................188Updating ..................................................187

Deleting Definitions ....................................188DESC

Category Definition Screen....................197

Dataset Access Screen ............................222SAM Profile Screen.................................211Script Definitions Screen........................217VSAM Profile Screen ..............................205

DLBLSAM Profile Screen.................................212

DLLs ................................................................52Download Script Name ................................99DRIVER

Category Definition Screen....................198DRIVER DATA

Category Definition Screen....................199Driver Specifications

BIMFTRD$ ...............................................307BIMFTRDB...............................................310BIMFTRDC ..............................................315BIMFTRDD ..............................................328BIMFTRDE...............................................330BIMFTRDF ...............................................337BIMFTRDI................................................345BIMFTRDJ................................................347BIMFTRDL...............................................351BIMFTRDM .............................................354BIMFTRDP...............................................356BIMFTRDQ ..............................................362BIMFTRDR...............................................365BIMFTRDT...............................................368BIMFTRDV ..............................................370BIMFTRDX...............................................375

Drivers...........................................................196DynaComm (APPC) ......................................64DynaComm/Elite ..........................................52

E

E(X)ITSAM Profile Screen.................................211VSAM Profile Screen ..............................207

EDIT TransfersAccess Security Definitions ...........223, 231Driver BIMFTRDE ..................................330Generic LIBQUE................................98, 102LIBQUE ....................................................196

Elite (APPC)....................................................64Emulators

1472/PC .....................................................52Attachmate Personal Client ...............52, 67Communications Manager/2..................65Configurator ..............................................53DLLS ...........................................................52DynaComm (APPC) .................................64DynaComm/Elite .....................................52

Index


Elite (APPC) .............................................. 64EXTRA ....................................................... 52FORVUS .................................................... 52HLLAPI ..................................................... 55IRMA ................................................... 52, 56IRMA (APPC) ........................................... 62Memorex ................................................... 52Novell ........................................................ 55NS/3270 .................................................... 52NS/Elite Plus ............................................ 52PC/3270............................................... 52, 66RUMBA ..................................................... 52RUMBA (APPC)....................................... 63Session IDs .......................................... 53, 54TLINK........................................................ 56TLINKW.................................................... 52

END KEYVSAM Profile Screen ............................. 208

EOF#OPTION

File Conversion Scripts ..................... 273EPIC Transfers

Dataset Access Definition Screen......... 221Dataset Access Security........................... 79Dataset Name Mask............................... 222Driver BIMFTRDF.................................. 337Generic LIBQUE............................... 98, 102LIBQUE ................................................... 196SAM Profile Screen ................................ 210

EXCLUDEPRINT Command................................... 264

EXITCategory Definition Screen................... 198

EXTRA............................................................ 52

F

Field DefinitionsFile Conversion Scripts.......................... 275

field(list)(list) format and rules ............................ 266Keywords ................................................ 265PRINT Command................................... 264Relational Operators.............................. 266Rules for Dates........................................ 266Rules for numbers .................................. 266Rules for string values........................... 267Rules for Times....................................... 266Samples.................................................... 268

File Conversion Scripts#CRLF...................................................... 290#END ....................................................... 293

#ERROR................................................... 286#GOTO .................................................... 285#GROUPBEG.......................................... 287#GROUPEND......................................... 287#IF ............................................................ 283#INSERT.................................................. 291#LINE ...................................................... 292#OPTION ................................................ 273#PROMPT ............................................... 280#RECORD ............................................... 279#SKIP ....................................................... 294ASCII........................................................ 273ASCII Files............................................... 301Character Strings.................................... 304Comments ............................................... 272DECIMALPT........................................... 273EOF........................................................... 273Field Definitions ..................................... 275Insert Literal............................................ 291Labels ....................................................... 282Occurs Depending On ........................... 298OUTPUT.................................................. 273Processing Options................................. 273Putting it all together ............................. 295Record Descriptions............................... 279SEPARATOR .......................................... 273Syntax ...................................................... 272Testing Your Script ................................ 305

File Upload Scripts........................................ 96#END ....................................................... 184#GOTO .................................................... 182#IF ............................................................ 180#INCLUDE.............................................. 181#OPTION ................................................ 175#PROMPT ............................................... 177CMDPFX= ............................................... 175CONTINUE= .......................................... 176DATEFMT=............................................. 175Labels ....................................................... 179LBLPFX= ................................................. 175Processing Options................................. 175Sample ..................................................... 185VARPFX= ................................................ 176

FORVUS ......................................................... 52

G

General Settings Dialog................................ 92Generic Masks

#DOWNLOAD....................................... 135Access Security Definitions................... 224DATASET NAME MASK ..................... 222

Index


LIBQUE ....................................................197LIBQUE Selection

Downloads ............................................98Uploads ...............................................102

PC Program Selection...............................97GROUPS

User Definition Screen ...........................202

H

HEX PAD CHARACTERSAM Profile Screen.................................213

Hexadecimal Notation ................................463HLLAPI...............................................52, 54, 55Host Activity Log for MVS.....................33, 37Host Activity Log for VSE......................22, 25Host Transfer File ........................................307HOSTAFT

#KEEP script statement..................127, 160#SENDTO script statement ...........128, 160Activate Script Screen ............................249

JOBNAME...........................................249SCRIPT ................................................249UPARMS .............................................249

Activating PC ..........................................162Activating Script In Batch......................163Activating Script In CICS.......................172Activating Script on Host ......................163BIMFTRBC

APPL Definitions ...............................164CICS Definitions.................................165Commands and Operands................166CONNECT Command ......................168HOSTAFT Command........................169MVS JCL..............................................166OPTION Command...........................167UPARM Command............................171VSE JCL ...............................................166VTAM Definitions..............................164

Deactivating PC ......................................162Driver BIMFTRDX..................................375Log Display Screen .................................248Monitoring Status ...................................160Script Definition Screen .........................216Script examples .......................................161Script List .................................................215Script Overview ......................................160Script Recording......................................117Script Syntax............................................126Status Detail Screen ................................244

#KEEP..................................................245CMD.....................................................245

JOBNAME...........................................245LAST ....................................................245NETNAME..........................................246NETNAME STATUS .........................246SCRIPT.................................................245START..................................................245STATUS ...............................................245UPARMS .............................................245

Status List.................................................242Transfer Log

CONNECTION ..................................258JOBNAME...........................................258SCRIPT.................................................258TFR-TYPE............................................258

Variable Substitution..............................162HOSTAFT Command..................................169

I

ICCF TransfersAccess Security Definitions ...........223, 234Driver BIMFTRDI ...................................345LIBQUE ....................................................196

IDCAMS Definitions ...................................322#END........................................................322#IDCAMS.................................................322#MAXCC= ...............................................323#NRECS= .................................................323#RECSZ=..................................................323#VOL=......................................................323%AVGSZ ..................................................324%CATDNM .............................................324%CATDSN...............................................324%CLUSTER..............................................324%DLBL .....................................................324%NRECS ..................................................324%NRECS10 ..............................................325%NRECS25 ..............................................325%NRECS50 ..............................................324%RECSZ ...................................................324%SAMAVGSZ .........................................325%SAMMAXSZ.........................................325%SAMRECFM.........................................325%VOL .......................................................324

INCLUDEPRINT Command ...................................264

IND$ TransfersDriver BIMFTRD$...................................307LIBQUE ....................................................196

Installation for MVSCICS Requirements...................................34Defining Control File ................................32

Index


Defining Log File...................................... 33Load Library ............................................. 29PC Program Installation.......................... 39Source Library .......................................... 29

Installation for VSECICS Requirements.................................. 23Defining Control File ............................... 21Defining Log File...................................... 22PC Program Installation.......................... 27Program Names........................................ 19

Interactive Interface (VSE)......................... 377Interface Settings Dialog .............................. 94IRMA .............................................................. 52IRMA (APPC)................................................ 62IRMA(DCA) E78+......................................... 56

J

JES TransfersAccess Security Definitions........... 223, 238Driver BIMFTRDJ................................... 347LIBQUE ................................................... 196

JOBNAMEHOSTAFT Activate Script Screen ........ 249HOSTAFT Status Detail Screen............ 245

K

Key FieldsCategory Definition Screen................... 195Dataset Access Screen............................ 221SAM Profile Screen ................................ 210Script Definitions Screen ....................... 217User Definition Screen........................... 201VSAM Profile Screen ............................. 204

L

LASTHOSTAFT Status Detail Screen............ 245

LBLPFX=File Upload Scripts................................. 175

LIBQUECategory Definition Screen................... 196Transfer Activity Log Display.............. 256

LIBR TransferBIMFTRDR.............................................. 365

LIBR TransfersAccess Security Definitions........... 223, 236Driver BIMFTRDB ................................. 310Driver BIMFTRDL ................................. 351Generic LIBQUE..................................... 102LIBQUE ................................................... 196

LINE=

Script Definitions Screen ....................... 218LOADNEXT

#OPTIONBIMAFT Scripts ................................. 130

LOG#OPTION

BIMAFT Scripts ................................. 130Log Settings Dialog....................................... 95LOGFILE

PRINT Command................................... 263LOGOFF


Logoff Scripts#AT ............................................................ 70#BYE .......................................................... 71#LOOK ...................................................... 69#SEND ....................................................... 70Recording A Script ................................... 75

LOGON#OPTION

BIMAFT Scripts ................................. 130Logon Scripts

#AT ............................................................ 70#BYE .......................................................... 71#LOOK ...................................................... 69#SEND ....................................................... 70Example ..................................................... 72Recording A Script ................................... 75

Logon/Logoff ScriptsScript Recorder ......................................... 74

LOOP#OPTION

BIMAFT Scripts ................................. 131Lower-Case Data......................................... 463LU/3270 Settings .......................................... 47LVL

Access Security Definitions................... 229

M

Memorex ........................................................ 52Messages

BIMFTR92-nnn ....................................... 428BIMFTR98-nnn ....................................... 428BIMFTR99-nnn ....................................... 430BIMFTRD$-nnn ...................................... 397BIMFTRDB-nnn...................................... 399BIMFTRDC-nnn...................................... 400BIMFTRDD-nnn ..................................... 403BIMFTRDE-nnn...................................... 405BIMFTRDF-nnn ...................................... 405

Index


BIMFTRDI-nnn........................................409BIMFTRDJ-nnn........................................410BIMFTRDL-22nn.....................................411BIMFTRDL-25nn.....................................411BIMFTRDL-nnn ......................................411BIMFTRDM-nnn .....................................411BIMFTRDP-nnn.......................................412BIMFTRDP-nnnn ....................................413BIMFTRDQ-nnn......................................413BIMFTRDR-nnn ......................................414BIMFTRDT-nnn ......................................415BIMFTRDV-nnn ......................................415BIMFTRDX-nnn ......................................417BIMFTRFI-nnnn ......................................441BIMFTRHC-nnn......................................417BIMFTRI1-nnn.........................................419BIMFTRI2-nnn.........................................419BIMFTRIP-nnn ........................................420BIMFTRLB-nnnn.....................................439BIMFTRPR-nnnn.....................................442BIMFTRSM-nnn ......................................421BIMFTRXP-nnn.......................................422BIMFTRxx-10nn ......................................443BIMFTRxx-11nn ......................................445BIMFTRxx-22nn ......................................447BIMFTRxx-25nn ......................................448BIMFTRxx-28nn ......................................449

N

NAMEDataset Access Screen ............................221SAM Profile Screen.................................211User Definition Screen ...........................202VSAM Profile Screen..............................207

NETNAMEHOSTAFT Status Detail Screen.............246Transfer Activity Log Display...............255

NETNAME STATUSHOSTAFT Status Detail Screen.............246

NEW#TRANSFER............................................140Category Definition Screen....................197

NEWEVENTSPRINT Command ...................................263

NEWEVENTSFINALPRINT Command ...................................263

NODELETE#TRANSFER............................................139

Novell..............................................................55NS/3270..........................................................52NS/Elite Plus .................................................52

LU/3270 Settings ......................................47

O

OperandsCoding Syntax .........................................461Comments ................................................464Continuation Syntax...............................462Dates .........................................................463Quoted Strings.........................................463Time ..........................................................463

OPTION Command.....................................167OUTPUT

#OPTIONFile Conversion Scripts......................273

P

PAD SHORT RECORDSSAM Profile Screen.................................213

PASSWORDUser Definition Screen............................201

PATH StatementAPPC ..........................................................61LU2/3270 ...................................................52

PAUSE#OPTION

BIMAFT Scripts ..................................131PC Program

ASCII Translation Option ......................104CRLF Transfer Option............................105Dialog Boxes ..............................................92Download Destination Dialog.................99Download Selection Dialog .....................97File Dialog ..................................................96File Pulldown ............................................88General Settings Dialog............................92Generic LIBQUE Selection

Downloads ............................................98Uploads ...............................................102

Generic Selection.......................................97Help Pulldown ..........................................91Installation for MVS..................................39Installation for VSE...................................27Interface Settings Dialog ..........................94Log Settings Dialog...................................95Signing On .................................................86Starting DOS Version ...............................84Starting OS/2 Version ..............................84Starting Windows 3.1 Version.................83Starting Windows 95/98/NT Version ...83Transfer Log...............................................90Transfer Pulldown ....................................90

Index


Upload Selection Dialog........................ 101PC/3270 ................................................... 52, 66PC-DOS Command Dialog........................ 119PDS Transfers

Dataset Access Definition Screen......... 221Dataset Access Security........................... 79Dataset Name Mask............................... 222Driver BIMFTRDD................................. 328Generic LIBQUE............................... 98, 102LIBQUE ................................................... 196

PF Key SummaryFTRL Transaction................................... 252FTRM Transaction.................................. 189

POWER TransfersAccess Security Definitions........... 223, 228Driver BIMFTRDP.................................. 356LIBQUE ................................................... 196

Print CommandSamples.................................................... 268

PRINT Command ....................................... 263ALLEVENTS........................................... 263EXCLUDE ............................................... 264field(list) .................................................. 264INCLUDE................................................ 264LOGFILE ................................................. 263NEWEVENTS ......................................... 263NEWEVENTSFINAL............................. 263

PROFILE#OPTION

BIMAFT Scripts ................................. 131SAM Profile Screen ................................ 211VSAM Profile Screen ............................. 205

Q

QSAM TransfersDataset Access Definition Screen......... 221Dataset Access Security........................... 79Dataset Name Mask............................... 222Driver BIMFTRDQ................................. 362Generic LIBQUE....................................... 98LIBQUE ................................................... 196

QUIT#OPTION

BIMAFT Scripts ................................. 131Quoted Strings ............................................ 463

R

RECFORMSAM Profile Screen ................................ 213

RECSIZESAM Profile Screen ................................ 213

RELOAD#OPTION

BIMAFT Scripts ................................. 131RENAME

#TRANSFER ........................................... 140REPLACE

#TRANSFER ........................................... 140Category Definition Screen ................... 197

Replacing Definitions ................................. 188Require User Definition

System Options Screen .......................... 191RETRY


RUMBA .......................................................... 52RUMBA (APPC)............................................ 63

S

S(select)Transfer Activity Log Display .............. 256

SAM Profile List .......................................... 209SAM Profile Screen ..................................... 210

(S)CRIPT.................................................. 211BIM-EPIC DSN ....................................... 212BLKSIZE .................................................. 213CRLF ........................................................ 212DESC........................................................ 211DLBL........................................................ 212E(X)IT....................................................... 211HEX PAD CHARACTER ...................... 213Key Fields................................................ 210NAME...................................................... 211PAD SHORT RECORDS........................ 213PROFILE.................................................. 211RECFORM............................................... 213RECSIZE.................................................. 213SECGRP................................................... 211TRANSLATE .......................................... 212TRUNCATE LONG RECORDS............ 213TRUNCATE TRAILING BLANKS ...... 214TYPES ...................................................... 212

SAM TransfersDataset Access Definition Screen ......... 221Dataset Access Security ........................... 79Dataset Name Mask............................... 222Driver BIMFTRDF.................................. 337Generic LIBQUE............................... 98, 102LIBQUE.................................................... 196SAM Profile List ..................................... 209SAM Profile Screen ................................ 210User Security Groups............................... 78

Index


Sample ScriptFile Upload Scripts .................................185

SCRIPT#UPLOAD ...............................................137HOSTAFT Activate Script Screen.........249HOSTAFT Status Detail Screen.............245SAM Profile Screen.................................211Script Definitions Screen........................217VSAM Profile Screen..............................207

Script Definitions List..................................215Script Definitions Screen.............................216

CMD .........................................................218COMMAND ............................................217DESC.........................................................217Key Fields ................................................217LINE= .......................................................218SCRIPT .....................................................217

SCRIPT TransfersAccess Security Definitions ...........223, 233

ScriptsAutomatic Transfer Scripts....................125File Conversion Scripts ..........................271File Upload Scripts .................................174HOSTAFT Script Overview...................160IDCAMS Definitions ..............................322Logoff Scripts ............................................69Logon Scripts.............................................69Maintaining on Host.......................215, 216Recording

Automatic Transfer Scripts...............117SECEXIT

Category Definition Screen....................198SECGRP

Access Security Definitions ...................229Category Definition Screen....................198Dataset Access Screen ............................222SAM Profile Screen.................................211VSAM Profile Screen..............................205

SEPARATOR#OPTION

File Conversion Scripts......................273SEQ

Access Security Definitions ...................229Session IDs................................................53, 54Settings Dialog

Auto ..........................................................115Connection.................................................42General .......................................................92Interface......................................................94Log ..............................................................95

START

#OPTIONBIMAFT Scripts ..................................132

HOSTAFT Status Detail Screen.............245Start Host Transaction.................................144Start Host Transaction Dialog....................118START KEY

VSAM Profile Screen ..............................208STATUS

HOSTAFT Status Detail Screen.............245STOP

#OPTIONBIMAFT Scripts ..................................132

SyntaxCoding Operands....................................461Comments ................................................464Continuation............................................462Date Operand ..........................................463Quoted Strings.........................................463Terminology ............................................461Time Operands........................................463

System Menu................................................190System Options Screen................................191

Activity Log .............................................192Alternate Maintenance Txn Codes .......192Default Security Exit...............................191Default Translate Table ..........................192Require User Definition .........................191

T

TCP/IPActivating...................................................57Connection Options ................................250De-activating .............................................57Overview....................................................57PC Settings .................................................49Setup (VSE) ................................................26

Temporary Storage Access .........................354TEMPSTG Transfers

Access Security Definitions ...........223, 240Time Operands.............................................463TLINK .............................................................56TLINKW..........................................................52Transfer Activity Log Display....................253

APPLID ....................................................255CATEGORY.............................................255LIBQUE ....................................................256NETNAME ..............................................255nnn(mmm) ...............................................256S(select).....................................................256USERID ....................................................255

Transfer Event Display ...............................259

Index


TRANSLATECategory Definition Screen................... 199SAM Profile Screen ................................ 212VSAM Profile Screen ............................. 207

TRTABLECategory Definition Screen................... 199

TRUNCATE LONG RECORDSSAM Profile Screen ................................ 213

TRUNCATE TRAILING BLANKSSAM Profile Screen ................................ 214

TYPEAccess Security Definitions................... 229

TYPESCategory Definition Screen................... 197SAM Profile Screen ................................ 212VSAM Profile Screen ............................. 208

U

UCATVSAM Profile Screen ............................. 208

UNIQUE#UPLOAD............................................... 137

UPARM Command .................................... 171UPARMS

HOSTAFT Activate Script Screen ........ 249HOSTAFT Status Detail Screen............ 245

Updating Definitions.................................. 187Upload Pacing ............................................... 51Upload Validation ........................................ 93User Definition List .................................... 200User Definition Screen ............................... 201

DATASET ACCESS ............................... 202GROUPS.................................................. 202Key Fields................................................ 201NAME...................................................... 202PASSWORD............................................ 201USER ID................................................... 201

USER IDUser Definition Screen........................... 201

USERIDTransfer Activity Log Display.............. 255

V

Variables#EXEC

%FNM................................................. 141%PNM................................................. 141%PTH.................................................. 141NOSUB ............................................... 141

Access Security Definitions%NETN............................................... 224

%NN.................................................... 224%PCUS................................................ 224%PU..................................................... 224%US ..................................................... 224%USER................................................ 224

Dataset Name Mask%CATN............................................... 222%DRVD............................................... 222%LIBQ................................................. 222%USER................................................ 222

Execute PC Program Dialog ................. 122File Upload Scripts

%DATE ....................................... 175, 183%PWD................................................. 183%TIME ................................................ 183%USER................................................ 183VARPFX.............................................. 176

Generic Uploads%DAT.................................................. 103%EXT................................................... 103%FNM ................................................. 103%GNM ................................................ 103%LNM................................................. 103%SNM ................................................. 103%TIM................................................... 103

HOSTAFT%JOBNAME....................................... 162%NETNAME...................................... 162%SCRIPT............................................. 162%UPn .................................................. 162UPARMS..................................... 245, 249

IDCAMS Definitions.............................. 324VARPFX=

File Upload Scripts................................. 176VSAM Profile List ....................................... 203VSAM Profile Screen .................................. 204

(S)CRIPT.................................................. 207CLUSTER ................................................ 208CRLF ........................................................ 207DATASET................................................ 205DATASET ACCESS ............................... 205DESC........................................................ 205E(X)IT....................................................... 207END KEY................................................. 208Key Fields................................................ 204NAME...................................................... 207PROFILE.................................................. 205SECGRP................................................... 205START KEY............................................. 208TRANSLATE .......................................... 207TYPES ...................................................... 208

Index


UCAT .......................................................208VSAM Transfers

Dataset Access Definition Screen..........221Dataset Access Security............................79Dataset Name Mask ...............................222Driver BIMFTRDC..................................315Driver BIMFTRDV..................................370Generic LIBQUE................................98, 102LIBQUE ....................................................196User Security Groups ...............................78VSAM Profile Screen..............................204VSAM Security..........................................79

VSE Interactive Interface ............................377VTAM Pacing.................................................51

Documents

PC/Transfer 1.8 Installatoin and Operations Guide