| SourceConnect for Mainframe Express and Revolve | Status Codes and Error Messages | |
| Install MFA base product mainframe software | Select this procedure if you are installing the mainframe MFA server for either the first time, installing additional MFA servers, or installing a higher level replacement MFA server. |
| Update your MFA clients/servers with a PTF package | Select this procedure if you are wanting to automatically apply maintenance to your current MFA clients and servers. It is highly recommended that you install the client software in a common LAN-based directory, so that the update will replace the executables shared by all users. |
| Upgrade the concurrent number of users limit to a higher level | Select this procedure if you have purchased a higher concurrent user limit and want to apply the higher limit to the mainframe servers. |
| E:mail id | If you wish to be automatically notified when PTF packages become available, then specify your e:mail id in this field. Once the Next button is pressed, your id will be sent to our ftp site, where it will be used for the master mailing list for MFA updates. If you wish to have more than one id placed on our ftp site, then specify the first id and press Next, then press Back on the next panel to return to this panel, where you can place another id to be registered. |
| High level qualifier to use for DSN's | This is the prefix to all dataset names created during the installation of the server. The maximum length of this prefix is 35 characters. A period '.' and the library name are appended to the prefix to form the library dataset name. The prefix must conform to MVS dataset naming conventions. |
| DASD unit name | This is the symbolic name for the disk drives on which you will be creating the datasets as a result of the installation process. This must be a valid name for your installation. |
| IBM RACF | Select this security system if you are using IBM's RACF, or no security at all. If you wish to install the MFA server without security active, then after the installation has completed, edit the INSTLIB member $MVSSEC and follow the instructions for turning off security. |
| CA Top Secret | Select this security system if you are using Computer Associate's Top Secret. You must define the MFA server as a facility to Top Secret. Failure to do this will cause an outstanding reply to be required from the console for the MFA server, thus making it appear that the client application has hung. |
| CA ACF/2 | Select this security system if you are using Computer Associate's ACF/2. You must define the MFA server with privileges "JOB STC" to ACF/2. |
Enter a valid job card. Each MFA jobstream will be generated using this job card information. You can copy and paste this job card from a 3270 emulator session if desired.
| Concurrent users activation code | This enablement code specifies the maximum number of users who can be logged on simultaneously. Each workstation application will issue a logon when the first file is opened and a logoff when the last file is closed. If two applications are running on the same workstation this will count as two concurrent users. |
| Optional Endevor activation code | If you are an Endevor user, purchased the MFA E/Option and wish to access Endevor through MFA, then an MFA E/Option Endevor activation code would have been provided with the product. |
| Install the MFA Standard server | Select this if you wish to install the base level MFA server. This server is used by all Drag and Dropclients, all Compare and Synchronize clients, and all SourceConnect and DataConnect clients. |
| Install the MFA CICS server | Select this if you wish to install the CICS DataConnect server for accessing datasets owned by CICS only. |
| Install the MFA Endevor server | Select this if you wish to install the E/Option MFA server. This server is used by all Drag and Drop clients, and all Compare and Synchronize clients that want to access Endevor files. |
| JES/2 | Select this if you are using a JES/2 spool system on your mainframe. |
| JES/3 | Select this if you are using a JES/3 spool system on your mainframe. |
| Librarian | Select this if you are using Computer Associates Librarian on your mainframe. |
| Panvalet | Select this if you are using Computer Associates Panvalet on your mainframe. |
| Name of Librarian executable | In order for MFA to add or replace members into Librarian, it must invoke the specified Librarian module. If your installation has changed the name of this module, or you wish to have MFA call a different one, then alter the name of the module. |
| Name of Panvalet executable | In order for MFA to add or replace members into Panvalet, it must invoke the specified Panvalet module. If your installation has changed the name of this module, or you wish to have MFA call a different one, then alter the name of the module. |
| Data type | When MFA add a new member of type data, it will use the specified value to inform Panvalet about the member type. |
| COBOL type | When MFA add a new member of type data, it will use the specified value to inform Panvalet about the member type. |
| PL/I type | When MFA add a new member of type data, it will use the specified value to inform Panvalet about the member type. |
| BAL type | When MFA add a new member of type data, it will use the specified value to inform Panvalet about the member type. |
| JCL type | When MFA add a new member of type data, it will use the specified value to inform Panvalet about the member type. |
| TCP/IP DirectConnect | Select DirectConnect if you are wish to access the mainframe directly from the workstation using a static pre-defined IP port. This is the preferred method of connection, as it does not require a long-running daemon on a workstation somewhere. You may have both DirectConnect and DaemonConnect if desired. |
| TCP/IP DaemonConnect | Select DaemonConnect if you wish to access the mainframe indirectly from the workstation using a variable unknown IP port. This method will require a long-running CCITCP2 daemon to be started on a workstation located somewhere in the network. You may have both DirectConnect and DaemonConnect if desired. |
| VTAM | Select VTAM if you wish to access the mainframe server through an APPC connection. This will require a 3rd party APPC stack to be installed on each workstation. |
Select the TCP/IP communication stack and release level in effect at your installation.
| Name of standard MFA server | This is the name given to the JCL member which is used to execute the MFA standard server. This JCL is placed into a system procedure library so it can be used by the MVS console operator to start the server procedure. |
| Name of TCP/IP started mainframe task | This is the name specified when TCP/IP support for the IBM mainframe is started. |
| Permanent TCP/IP port number for MFA | DirectConnect support requires a non-changing assigned port number to listen to. Your TCP/IP administrator can tell you a specific number to use. This is the value that is used by the workstation clients in the MFNODE:ipaddress,MFPORT:port configuration parameter. |
| Mainframe TCP/IP address to bind with | (Optional) This is the TCP/IP address that you wish to have the mainframe bind with. Normally, the first IP address on the HOST statement in the TCP/IP mainframe configuration is used, but if this is not the correct address, or if the primary adapter statement is not set to the same ring, then you must force the mainframe server to use a specific IP address. A TCP/IP address takes the form nnn.nnn.nnn.nnn where nnn has a value from 001 to 255. The periods separating the IP address segments are not entered on the screen. |
| Name of TCP/IP started mainframe task | This is the name specified when TCP/IP support for the IBM mainframe is started. |
| Name this server is to be known by | DaemonConnect support requires a non-changing name to be assigned to the server. This is the name that is used by the workstation clients in the configuration server name. |
| Workstation TCP/IP address of daemon | This is the TCP/IP address of the long-running workstation CCITCP2 daemon process, that you wish to have the mainframe bind with. A TCP/IP address takes the form nnn.nnn.nnn.nnn where nnn has a value from 001 to 255. The periods separating the IP address segments are not entered on the screen. |
| Mainframe TCP/IP address to bind with | (Optional) This is the TCP/IP address that you wish to have the mainframe bind with. Normally, the first IP address on the HOST statement in the TCP/IP mainframe configuration is used, but if this is not the correct address, or if the primary adapter statement is not set to the same ring, then you must force the mainframe server to use a specific IP address. A TCP/IP address takes the form nnn.nnn.nnn.nnn where nnn has a value from 001 to 255. The periods separating the IP address segments are not entered on the screen. |
| Name of standard MFA server VTAM APPLID | This is the VTAM application name associated with this server. When configuring communications on the workstation this item is also known as the Partner LU. |
| Name of MFA standard loadlib | This is the dataset name of the PDS load library for the MVS servers. This library contains the run time executable programs and must be APF authorized. |
| Name of RLIO VCTL library | This is the name of the PDS library which will be used to contain dataset allocation information for new datasets, for DataConnect. |
| Name of MFA transid | This is the CICS transaction code which is used to initiate the CICS server. It must be 4 characters in length and the fourth character must be 'F'. |
| CICS library containing DFHECI | This is the name of the CICS library which contains the module DFHECI. The DFHECI module is link-edited with the CICS server at installation time. |
| Name of TCP/IP started mainframe task | This is the name specified when TCP/IP support for the IBM mainframe is started. |
| Permanent TCP/IP port number for MFA | DirectConnect support requires a non-changing assigned port number to listen to. Your TCP/IP administrator can tell you a specific number to use. This is the value that is used by the workstation clients in the MFNODE:ipaddress,MFPORT:port configuration parameter. |
| Mainframe TCP/IP address to bind with | (Optional) This is the TCP/IP address that you wish to have the mainframe bind with. Normally, the first IP address on the HOST statement in the TCP/IP mainframe configuration is used, but if this is not the correct address, or if the primary adapter statement is not set to the same ring, then you must force the mainframe server to use a specific IP address. A TCP/IP address takes the form nnn.nnn.nnn.nnn where nnn has a value from 001 to 255. The periods separating the IP address segments are not entered on the screen. |
| TCP library containing EZACICAL | This is the name of the TCP/IP library which contains the module EZACICAL. The EZACICAL module is link-edited with the TCP/IP server at installation time. |
| Name of CICS MFA server VTAM APPLID | This is the VTAM application name associated with this server. When configuring communications on the workstation this item is also known as the Partner LU. |
| Name of mainframe volume | This is the name of a permanent mainframe volume that will be used to define a few VSAM cluster on for use by the MFA server.. |
| Name of MFA CICS loadlib | This is the dataset name of the PDS load library for the CICS server. This library contains the run time executable programs and must be appended to the DFHRPL DD statements in the CICS startup JCL. |
| Name of Endevor MFA server | This is the name given to the JCL member which is used to execute the MFA E/Option server. This JCL is placed into a system procedure library so it can be used by the MVS console operator to start the server procedure. |
| Name of Endevor loadlib | This is the name of your current Endevor system's load library.. |
| Name of Endevor conlib | This is the name of your current Endevor system's CONLIB library. If you do not use a CONLIB, then specify the Endevor loadlib again. |
| Name of Endevor ESI loadlib | (Optional) If, and only if, you are using the optional Endevor External Security Interface for additional Endevor security, then specify the name of this ESI load library. |
| Name of TCP/IP started mainframe task | This is the name specified when TCP/IP support for the IBM mainframe is started. |
| Permanent TCP/IP port number for MFA | DirectConnect support requires a non-changing assigned port number to listen to. Your TCP/IP administrator can tell you a specific number to use. This number must be different from the standard server's. This is the value that is used by the workstation clients in the MFNODE:ipaddress,MFPORT:port configuration parameter. |
| Mainframe TCP/IP address to bind with | (Optional) This is the TCP/IP address that you wish to have the mainframe bind with. Normally, the first IP address on the HOST statement in the TCP/IP mainframe configuration is used, but if this is not the correct address, or if the primary adapter statement is not set to the same ring, then you must force the mainframe server to use a specific IP address. A TCP/IP address takes the form nnn.nnn.nnn.nnn where nnn has a value from 001 to 255. The periods separating the IP address segments are not entered on the screen. |
| Name of TCP/IP started mainframe task | This is the name specified when TCP/IP support for the IBM mainframe is started. |
| Name this server is to be known by | DaemonConnect support requires a non-changing name to be assigned to the server. This is the name that is used by the workstation clients in the configuration server name. |
| Workstation TCP/IP address of daemon | This is the TCP/IP address of the long-running workstation CCITCP2 daemon process, that you wish to have the mainframe bind with. A TCP/IP address takes the form nnn.nnn.nnn.nnn where nnn has a value from 001 to 255. The periods separating the IP address segments are not entered on the screen. |
| Mainframe TCP/IP address to bind with | (Optional) This is the TCP/IP address that you wish to have the mainframe bind with. Normally, the first IP address on the HOST statement in the TCP/IP mainframe configuration is used, but if this is not the correct address, or if the primary adapter statement is not set to the same ring, then you must force the mainframe server to use a specific IP address. A TCP/IP address takes the form nnn.nnn.nnn.nnn where nnn has a value from 001 to 255. The periods separating the IP address segments are not entered on the screen. |
| Name of Endevor MFA server VTAM APPLID | This is the VTAM application name associated with this server. When configuring communications on the workstation this item is also known as the Partner LU. |
| Name of MFA E/Option loadlib | This is the dataset name of the PDS load library for the E/Option server. This library contains the run time executable programs and must be APF authorized. |
| Name of Endevor JCL library | This is the name of the PDS library which will be used to contain dataset skeleton JCL for the Endevor processors. |
| Name of Endevor environment | MFA must create modules to be placed into your Endevor system. Specify the environment to be used, and this must be available at run-time for this server. |
| Name of Endevor system | MFA must create modules to be placed into your Endevor system. Specify the system to be used, and this must be available at run-time for this server. |
| Name of Endevor subsystem | MFA must create modules to be placed into your Endevor system. Specify the subsystem to be used, and this must be available at run-time for this server. |
| Loadlib created | One or two dataset names are provided that must be APF authorized in your mainframe environment. |
| Loadlib created | One or two dataset names are provided that must be APF authorized in your mainframe environment. |
| For CA Top Secret | You must define the MFA server as a facility to Top Secret. Failure to do this will cause an outstanding reply to be required from the console for the MFA server, thus making it appear that the client application has hung. |
| Loadlib created | One or two dataset names are provided that must be APF authorized in your mainframe environment. |
| For CA ACF/2 | You must define the MFA server with privileges "JOB STC" to ACF/2. |
| Upload using an existing MFA server | Good news, if you already have MFA running and are simply installing a new release, or an additional server, then you can take advantage of the power of MFA. By selecting this method, the installation program can automatically allocate new datasets, determine your environment, upload the modules and even submit the generated JCL. |
| Upload using an external manual method | If MFA is not yet installed on your system, then select this method, and the JCL streams will be generated for you. Instructions will also be provided, on what files are to be transfered, to where, and whether they are binary or text. |
| User identification | Specify the user identification to be used for this software installation. Make sure that this userid has the appropriate dataset authorization. |
| Password | Specify the password associated with the userid given. |
| Current MFA server name | (Optional) Specify the name of the standard mainframe server, as known to the CCI daemon. If you are not using the CCI daemon, and using direct connect TCP/IP instead, then specify the name of the started mainframe task. |
| Current MFA machine parms | (Optional) Specify the machine parameters of any current MFA server that is running. If you are using APPC, or direct connect TCP/IP then you will need to enter information here. For APPC, you would most likely enter the LUname.mode, for example WKSLU010.#INTER where WKSLU010 is your LU name. For TCP/IP direct connect, you would enter MFNODE:xxx.xxx.xxx.xxx,MFPORT:yyyy where xxx.xxx.xxx.xxx would be the IP address, or DNS name of your mainframe, and yyyy would be the assigned TCP/IP port that the standard mainframe server is to listen on. To determine these values, you may refer to the $MFATCP member in the mainframe INSTLIB dataset. |
| Notes located in | Detailed notes on completing the installation process have been generated and are located in the C:\MicroFocusMFA directory, under the file name NOTES. This file will be displayed using Notepad once the setup program has been finished. Follow these notes to complete the installation. |
| Installation dataset | The name of the mainframe installation dataset is given. Detailed notes on completing the installation process have been generated and are located in the C:\MicroFocusMFA directory, under the file name NOTES. This file will be displayed using Notepad once the setup program has been finished. Follow these notes to complete the installation. |
| Access the MERANT ftp site and download the PTF pack | Select this process if you have Internet access to the outside world. The maintenance process will automatically access the correct ftp site, determine the highest PTF package level available for your server, and download the PTF package to the C:\MicroFocusMFA directory. Make sure that you have at least 10 megabytes of free disk space on your C drive. |
| I have already downloaded the PTF pack to C:\MicroFocusMFA | Select this process if you do not have Internet access
to the outside world. You will need to access the MERANT ftp site (ftp://ftp.merant.com/middleware/mfa/)
and download to the C:\MicroFocusMFA directory, the highest level PTF
package. Make sure that you have at least 10 megabytes of free disk
space on your C drive. |
| Update the MFA Standard server | Select this if you wish to update the base level MFA server. This server is used by all Drag and Dropclients, all Compare and Synchronize clients, and all SourceConnect and DataConnect clients. |
| Update the MFA CICS server | Select this if you wish to update the CICS DataConnect server for accessing datasets owned by CICS only. |
| Update the MFA Endevor server | Select this if you wish to update the E/Option MFA server. This server is used by all Drag and Drop clients, and all Compare and Synchronize clients that want to access Endevor files. |
| Name of installation library | The name of this library is remembered from the server installation process, but if for some reason it has been changed, then alter the name here. |
| Name of standard object library | (Optional) The name of this library is remembered from the server installation process, but if for some reason it has been changed, then alter the name here. |
| Name of CICS object library | (Optional) The name of this library is remembered from the server installation process, but if for some reason it has been changed, then alter the name here. |
| Name of standard load library | The name of this library is remembered from the server installation process, but if for some reason it has been changed, then alter the name here. |
| Name of CICS load library | (Optional) The name of this library is remembered from the server installation process, but if for some reason it has been changed, then alter the name here. |
| Name of E/Option load library | (Optional) The name of this library is remembered from the server installation process, but if for some reason it has been changed, then alter the name here. |
| You have successfully completed the update to your workstation of the MFA PTF package. |
| You have successfully registered with MERANT to be notified for future updates. |
| User identification | Specify the user identification to be used for this application. Make sure that this userid has the appropriate dataset authorization. |
| Current Password | Specify the password associated with the userid given. |
| New Password | If you wish to change your mainframe password, enter the new one here and repeat it in the repeat password field. |
| Repeat Password | If you are changing your mainframe password, the new password must be entered the new password field, and repeated in the repeat password field. |
| Catalog search criteria, delimited by commas | This required field is passed to the mainframe in order to obtain a list of data sets that match the fully qualified name, a partial name, or a name that contains an asterisk for additional matching possibilities. You may specify multiple search criteria in the same line, separated by commas or semi-colons. The last twenty catalog search criteria items are kept and may be selected directly from the drop down. |
| Minutes of inactivity before logoff | If you wish to have Drag and Drop automatically log you off the mainframe after a period in inactivity, then enter the number of minutes desired. Specifying zero will de-activate this feature. |
| CCI Communication Type | Select either TCP/IP or VTAM's APPC as your communication method. You must make sure that the appropriate communication stack has been installed. |
| Standard Server Name | (Optional) Specify the name of the standard mainframe server, as known to the CCI daemon. If you are not using the CCI daemon, and using direct connect TCP/IP instead, then specify the name of the started mainframe task. |
| Standard Server IP node and Port | (Optional) Specify the machine parameters of any current MFA server that is running. If you are using direct connect TCP/IP then you will need to enter information here. You would enter either the DNS name of your mainframe, or the IP address in the form xxx.xxx.xxx.xxx for the IP node, and the assigned port number of the MFA server in the form yyyy for the port. To determine these values, you may refer to the $MFATCP member in the mainframe INSTLIB dataset. |
| Standard Server LU name and Mode | Specify the LU name and mode to be used with this APPC connection. Typically, #INTER is the usual mode to be used. |
| Endevor Server Name | (Optional) Specify the name of the MFA E/Option mainframe server, as known to the CCI daemon. If you are not using the CCI daemon, and using direct connect TCP/IP instead, then specify the name of the started mainframe task. |
| Endevor Server IP node and Port | (Optional) Specify the machine parameters of any current MFA server that is running. If you are using direct connect TCP/IP then you will need to enter information here. You would enter either the DNS name of your mainframe, or the IP address in the form xxx.xxx.xxx.xxx for the IP node, and the assigned port number of the MFA server in the form yyyy for the port. To determine these values, you may refer to the $MFATCP member in the mainframe INSTLIB dataset. |
| Endevor Server LU name and Mode | Specify the LU name and mode to be used with this APPC connection. Typically, #INTER is the usual mode to be used. |
| Catalog search criteria, delimited by commas | This required field is passed to the mainframe in order to obtain a list of data sets that match the fully qualified name, a partial name, or a name that contains an asterisk for additional matching possibilities. You may specify multiple search criteria in the same line, separated by commas or semi-colons. The last twenty catalog search criteria items are kept and may be selected directly from the drop down. |
| Endevor qualification | If you are an Endevor user and have purchased and
installed from MERANT the E/Option interface add-on product to MFA, then
you can access the Endevor system by specifying the proper
qualification. It must be in the form, and typically the specification
would consist of at least the ENV parameter, and optionally followed by
the SYS, SUB, or STG parameters. The JCARD, JMBR and JLIB parameters are
only required if your wish to override the defaults already defined in
that particular Endevor library.
ENV environment SYS system SUB subsystem STG stage id JCARD jobcardmember JMBR EndevorJCLmember JLIB EndevorJCLlibrary You can include quotes around any variables specified in the Endevor qualification area, if so desired. For example, ENV 'PROD' SYS 'ATM' SUB 'USA' would be a valid specification as well as ENV PROD SYS ATM SUB USA. The last Endevor qualifications are kept in the most recently used, first order, and may be selected directly from the drop down. All of these qualifications in the list will appear on the mainframe window. |
| Use codepage | The workstation code page that is used when performing ASCII to EBCDIC, and EBCDIC to ASCII translations, is sent to the mainframe during the initial connection. The default workstation codepage may not be desired for non-North American workstations, or non-Mainframe Express users. By setting this field to the proper codepage, the associated codepage is sent to the mainframe, instead of the workstation default one. By setting this field to mainframe default, no codepage is sent from the workstation, but instead the default mainframe translate tables located in MFLSCTRN on the mainframe will be used instead. The proper tables must have been selected during the mainframe installation of the server. |
| Limit browse lines to | This numeric field limits the number of lines that will be read and transferred when double clicking on a file or member. If you specify zero, there is no limit. |
| Default editor specification | You may specify the command and any optional parameters for a default editor to be used, when using the right mouse context button for the edit function. This default editor will be used, unless a Windows editor for the specific file extension has already been set up. You must fully qualify the editor command, include the path and extension of the program to invoke. |
| EBCDIC/ASCII translation | Set this flag for each data set type that is to be translated to/from ASCII/EBCDIC. |
| Warn if the target name does not match the source | Set this flag if you want to be warned that dragging a file or member would result in the target file having a different name from the source file. |
| Warn if the target exists | Set this flag if you want to be warned when dragging a file or member if the file already exists. Note that there is an overhead when using this flag as the mainframe must be checked for the existence of the file or member. |
| Warn if the source files contain embedded hex | Set this flag if you want to be informed in an imported source file contains unusual or unprintable characters. |
| Use MDECONV style embedded hex processing | This method, when selected, will detect all imbedded hex values that translate to less than x'20' and insert a null byte in front of each of them. This is the Micro Focus Workbench MDECONV technique, and all Micro Focus COBOL applications will properly detect this. |
| Inform when submitted jobs have completed | Set this flag if you wish to be informed when your submitted jobstream has finished. |
| Inform when migrated datasets have been recalled | Set this flag if you want to be informed when a dataset you have asked to be recalled has completed. |
| Scan imported members for copy statements | Set this flag if you want to have the file or member being dragged from the mainframe checked for copy type statements and allow an automatic import of the related copy files. |
| Prompt for an extension on import | Set this flag if you want to ensure that a dragged member will be written out with a PC extension. |
| Refresh workstation member lists after subsetting | Set this flag if you want to force a refreshed member list after using the directory subsetting feature. There is a small overhead to this option. |
| Refresh mainframe member lists after subsetting | Set this flag if you want to force a refreshed member list after using the directory subsetting feature. There is a small overhead to this option. |
| Dataset name | Specify the dataset name to be created on the mainframe. |
| Quantity | Specify the number of either cylinders, tracks or blocks to be allocated. |
| Type | Select the type of dataset to be created. |
| Directory blocks | This field is present only for the allocation of partitioned datasets. It is to contain the number of directory blocks to be placed in the mainframe partitioned dataset. |
| Logical record length | Specify the logical record length of the dataset |
| Block size | (Optional) If specified, the dataset will be created with this block size, otherwise the mainframe operating system will select the appropriate block size to be used. |
| Volume | (Optional) If specified, the dataset will be created on this volume, otherwise the mainframe operating system will select the appropriate volume to be used. |
| SMS storage class | (Optional) If specified, the dataset will be created with this SMS storage class information. |
| SMS data class | (Optional) If specified, the dataset will be created with this SMS data class information. |
| Expiration date | (Optional) If specified, both the YYYY and DDD fields must be filled in, and must contain a valid 4 digit year and 3 digit day of year field. |
| Get DCB from existing dataset | Select this button if you wish to read the DCB information from a existing mainframe dataset, and populate some of the fields on this panel. |
| Specify the fully qualified mainframe dataset name that is to be looked up, so that some of the DCB information can be used to populate the fields in the allocate new dataset request. |
| Minimum record length | Specify the minimum record length to be associated with this workstation indexed file. |
| Maximum record length | Specify the maximum record length to be associated with this workstation indexed file. |
| Key position | The mainframe VSAM relative key position is displayed for indexed datasets. |
| Key length | The mainframe VSAM key length is displayed for indexed datasets. |
| System | Specify the LCM system to be used. |
| Config | Specify the LCM configuration to be used within this system |
| Lock member on download | If you wish to automatically have the member locked when downloaded, then select this option. |
| Type | Specify the LCM member type for this member. |
| Change name | Specify the change name to be associated with this update. |
| Type | Specify the Endevor member type for this member. |
| CCID | Specify any required change control identification for this member. |
| Comment | Specify any required comment for this member. |
| Type | Specify the Endevor member type for this member. |
| CCID | Specify any required change control identification for this member. |
| Comment | Specify any required comment for this member. |
| Signout member | If you wish to have the member automatically signed out, then select this option. |
| Override existing signout | If you wish to override any existing signout for this member, then select this option. |
| Type | Specify the Endevor member type for this member. |
| CCID | Specify any required change control identification for this member. |
| Comment | Specify any required comment for this member. |
| Override existing signout | If you wish to override any existing signout for this member, then select this option. |
| Bypass generate processor | If you wish to bypass any mainframe generation, then select this option. |
| Env | Specify the environment to be used for this update. |
| Sys | Specify the system to be used for this update. |
| Sub | Specify the subsystem to be used for this update. |
| Stg | Specify the stage to be used for this update. |
| Select the copy members you wish to have located and downloaded | You have been presented with a list of detected copy members. If you wish to import any of the members from the list, select one or more of them using the standard selection keys or mouse clicks. The copy file pattern matching algorithm tries to locate the proper copy file names, but since it is not a compiler, it will sometime pick up names that are not really copy files. |
| Search one or more mainframe dataset, each delimited by comma | This field allows you to specify the list of mainframe datasets, or source code control system libraries to search in. If the member is not found in the first dataset, then and only then is the next checked for the member. |
| Write copy members to directory or Mainframe Express dataset | This field allows you to alter the location that the copy members are to be stored into. You may also specify a Mainframe Express partitioned dataset. |
| Write members with extension | This field allows you to set or alter the file extension that the copy members are to be stored as. |
| Download all records | Select this option if all of the mainframe records are to be retrieved for the download. |
| Download record by low/high key range | Select this option if you wish to select records within a range. You may specify the lower key to select a starting range, or the upper key to select an ending range, or both keys for a lower and upper range. The data entered in this field is not converted to upper case. In addition, you may specify hexadecimal data in either of these fields by specifying hex bytes within X' ', such as X'C140C2E7F0'. Greater than and equal searches are done for the lower key, and less than or equal searches are done for the upper key. |
| Limit record count to the first | Select this option if the first N records are to be downloaded from the file. |
| Download all records | Select this option if all of the mainframe records are to be retrieved for the download. |
| Limit record count to the first | Select this option if the first N records are to be downloaded from the file. |
| Database name | This field specifies the name of the PCIMS database to load. |
| Location of segment name in data record | This field defines the offset in the unloaded database sequential file layout that the reload utility is to find the starting byte of the segment name. This field is relative to 1. |
| Location of segment data in data record | This field defines the offset in the unloaded database sequential file layout that the reload utility is to find the starting byte of the segment data. This field is relative to 1. |
| Location | This field specifies the name of the location containing the target table. If not specified, then the default location is used. You must use the mainframe DSNTIAUL utility to create the source data file. |
| Authid | This field specifies the authorization identifier of the table. |
| Table name | This field specifies the name of the table to be replaced. |
| EBCDIC code page | This field defines the mainframe code page in use. |
| ASCII code page | This field defines the workstation code page in use. |
| Page size | This field defines whether you wish to use a 4K or 32K page. |
| Specify the name of the subdirectory to be created. |
| Specify the new name of the member. |
| Alter the name, if desired, that the file is to be pasted as. |
| Specify the member subsetting to be performed. You may
specify a specific member name, or use filter characters to be creative
about a collection of members to be displayed. The filter characters are
imbedded with any other characters for pattern matching of the member
name, similar to the usage of the wildcard characters on the workstation
directory command. The filter characters are:
* any character may follow ? any character in this position + the character in this position must be non-blank - the character in this position must be a blank / the character in this position must be numeric \ the character in this position must be non-numeric |
| Specify the member type subsetting to be performed.
You may specify a specific member type, or use filter characters to be
creative about a collection of member types to be displayed. The filter
characters are imbedded with any other characters for pattern matching
of the member type, similar to the usage of the wildcard characters on
the workstation directory command. The filter characters are:
* any character may follow ? any character in this position + the character in this position must be non-blank - the character in this position must be a blank / the character in this position must be numeric \ the character in this position must be non-numeric |
| Specify the extension this dataset is to be associated with. |
| Specify the directory subsetting to be performed. You
may specify a specific file, or use filter characters to be creative
about a collection of files and extensions to be displayed. The filter
characters are imbedded with any other characters for pattern matching
of the file or extension, identical to the usage of the wildcard
characters on the workstation directory command. The filter characters
are:
* any character may follow ? any character in this position |
| Specify the extension this file is to be written with. |
| Specify the file name and optional extension this dataset is to be written as. |
| Specify the model for the new MFE partitioned dataset. |
| Specify the model for the new MFE sequential or VSAM dataset. |
The Micro Focus Data Access Services File Transfer Utility (commonly known as Drag and Drop) provides a powerful drag-and-drop style GUI access to mainframe datasets, including support for the following data types:
You may drag files, individual members, or entire sets of members from the mainframe to the workstation, or back again. When importing from the mainframe, support for all file types is provided. When exporting from the workstation, support for most file types is available. In order for you to use this utility, the Micro Focus Mainframe Access Product must be purchased and successfully installed on your mainframe system.
The utility provides two scalable windows on the desktop. The left hand window provides a list of the workstation drives, directories and files. To expand a drive or directory, double click on the desired name. To contract an expanded drive or directory, double click again on the desired name. To browse a specific file, double click on the desired name. The field icon may be used in place of the right mouse context button. You may reposition a member list by using any alphabetic key. The right hand window provides a list of the mainframe datasets that are related to the catalog search criteria, asked for during the configuration options at initial start-up. The utility attempts to determine the dataset type, but certain files are impossible to determine. To inform the utility of the dataset type, single click on the right hand mouse button over the desired dataset to view the context menu. You may select the appropriate dataset type from the list. The utility will store this selection so that you do not have to repeat this process for this dataset. To expand a partitioned, Librarian, Panvalet, Endevor, LCM dataset, or JES spool double click on the desired dataset. To contract an expanded dataset, double click again on the desired dataset. To browse a specific dataset or member, double click on the desired name. The drag and drop utility supports multiple selection as well as single selection for its actions. This works in the same way as other utilities available with the operating system. If you select an item by single-clicking on it without having either the Ctrl or Shift key depressed, then only that item will be selected and any other selected items in the same window will be de-selected for you. If you select an item by single-clicking on it and have the Ctrl key depressed, then the item selected will join any other selected items in the same window. If you select an item by single-clicking on it and have the Shift key depressed, then all items in the range of the last non-Shift selection to this line item will be selected. To copy a dataset, file or member from one platform to the other, you must: hold down the left mouse button over a desired dataset or file drag it over to the opposite window position the mouse over the desired target location release the mouse You may drag entire mainframe partitioned, Librarian, Panvalet, Endevor or LCM datasets, if you wish to copy all members to the workstation, or simply drag an individual file, or member if you wish to copy them one at a time. Likewise, the same can be done with workstation directories and files that are to be copied to the mainframe. All VSAM datasets, when copied from the mainframe to the workstation, are automatically converted to the appropriate workstation file format. For these files, however, the EBCDIC to ASCII conversion is not performed. You must use the Micro Focus Data File Convertor Utility (DFCONV) on your own.
The high performance Data Access Services is a drag and drop style utility. To copy files to and from the mainframe, simply single-click on the desired file names, and drag them to the required location in the opposite window. Entire directories or datasets, containing multiple files can be dragged, if desired. To set global options, use the Options action in the Configure pull-down. To set specific types for mainframe datasets, use the right mouse context button over the desired mainframe dataset name. To expand the drive, directory, or mainframe dataset, and produce a member list, double-click on the desired item. To contract these expanded lists, double-click once again. To display a limited number of lines of a workstation file or a mainframe dataset or member, double-click on the desired item to produce a browse window. The browse limit can be altered by using the Options action. The drag and drop utility supports multiple selection as well as single selection for its actions. This works in the same way as other utilities available with the operating system. If you select an item by single-clicking on it without having either the Ctrl or Shift key depressed, then only that item will be selected and any other selected items in the same window will be de-selected for you. If you select an item by single-clicking on it and have the Ctrl key depressed, then the item selected will join any other selected items in the same window. If you select an item by single-clicking on it and have the Shift key depressed, then all items in the range of the last non-Shift selection to this line item will be selected. You may dynamically alter the mainframe list of datasets by changing the 'Catalog search criteria' field by using the 'Options' action under the 'File' pull-down. You may dynamically alter the mainframe Endevor qualification by changing the 'Endevor qualification' field by using the 'Options' action under the 'File' pull-down.
| User identification | Specify the user identification to be used for this application. Make sure that this userid has the appropriate dataset authorization. |
| Current Password | Specify the password associated with the userid given. |
| CCI Communication Type | Select either TCP/IP or VTAM's APPC as your communication method. You must make sure that the appropriate communication stack has been installed. |
| Standard Server Name | (Optional) Specify the name of the standard mainframe server, as known to the CCI daemon. If you are not using the CCI daemon, and using direct connect TCP/IP instead, then specify the name of the started mainframe task. |
| Standard Server IP node and Port | (Optional) Specify the machine parameters of any current MFA server that is running. If you are using direct connect TCP/IP then you will need to enter information here. You would enter either the DNS name of your mainframe, or the IP address in the form xxx.xxx.xxx.xxx for the IP node, and the assigned port number of the MFA server in the form yyyy for the port. To determine these values, you may refer to the $MFATCP member in the mainframe INSTLIB dataset. |
| Standard Server LU name and Mode | Specify the LU name and mode to be used with this APPC connection. Typically, #INTER is the usual mode to be used. |
| Endevor Server Name | (Optional) Specify the name of the MFA E/Option mainframe server, as known to the CCI daemon. If you are not using the CCI daemon, and using direct connect TCP/IP instead, then specify the name of the started mainframe task. |
| Endevor Server IP node and Port | (Optional) Specify the machine parameters of any current MFA server that is running. If you are using direct connect TCP/IP then you will need to enter information here. You would enter either the DNS name of your mainframe, or the IP address in the form xxx.xxx.xxx.xxx for the IP node, and the assigned port number of the MFA server in the form yyyy for the port. To determine these values, you may refer to the $MFATCP member in the mainframe INSTLIB dataset. |
| Endevor Server LU name and Mode | Specify the LU name and mode to be used with this APPC connection. Typically, #INTER is the usual mode to be used. |
| Title | This option instructs the monitor to place the text on the application task bar. This allows you to easily identify a specific monitor session from the task list. |
| Startup | This option instructs the monitor to start up at a specified time. This is generally used in conjunction with the wakeup option. If used, the format is in 24 hour time, and must be in the range of 00:00 to 23:59. |
| Wakeup | This option instructs the monitor on how long it is to remain dormant after the initial analysis has completed but before analyzing the environment for subsequent changes to be processed. The default is to remain dormant for 8 hours. |
| Perform this many monitor iterations before shutting down | This option instructs the monitor on how many times it is to do the analysis scan. The default is forever, but if you wish to invoke this process a limited number of times, then specify a value. |
| Allow a maximum of this many transfers in an iteration | This option instructs the monitor to limit the number of imports or exports it does per cycle to the specified value. The default is to transfer all required files. |
| Clean up mainframe connection after this many transfers | This option instructs the monitor to automatically terminate the connection to the mainframe and then initiate a new connection after a specified number of mainframe server requests. This parameter is useful, as with some mainframe source code control systems, and operating system functions, some mainframe memory gets allocated and not freed by the routines called by the MFA server subtasks. This memory tends to accumulate and make the MFA server's memory usage increase. By setting a value to cause this automatic termination and re-connection, this so-called dead memory, tends to get freed up. Generally, disconnections and connections are fairly fast, so a reasonable value for this parameter would be about 500. |
| Delete workstation file if mainframe member is deleted | This option instructs the monitor to delete workstation files, when it notices that the corresponding mainframe member has been deleted. This is especially useful in environments that do promotions of mainframe members to higher level datasets, and want to mirror this promotion on the workstation. The default is to ignore this situation and not delete the workstation files. |
| Handle imbedded hex in the Micro Focus MDECONV format | This option indicates that you wish to have all source code imbedded hex values handled in the same way as the Workbench MDECONV application, in that all translated hex values less than x'20' will have a null character inserted before the hex value. The COBOL run-time system will properly handle these imbedded hex values. Revolve users may or may not want to turn on this option. |
| Monitor the following | A list of workstation/dataset monitor relationships is provided. Use the Add button to add a new relationship, the Remove button to delete a selected relationship, or the Configure button to alter a selected relationship. |
| Select the dataset type to be monitored | Specify the type of the mainframe dataset that a relationship is to be build. |
| Specify the dataset name to be monitored | Enter the fully qualified mainframe dataset name to be monitored. |
| Specify the Librarian dataset name to be monitored | Enter the fully qualified name of the mainframe Librarian dataset to be monitored. |
| Specify the optional type, with or without filter characters | If your installation has gone to the trouble of
setting up valid Librarian types on the mainframe, then you can take
advantage of this information in selecting specific member types for you
monitor relationship. You may specify a specific type, or use filter
characters to be creative about a collection of types to be monitored.
The filter characters are imbedded with any other characters for pattern
matching of the Librarian type, similar to the usage of the wildcard
characters on the workstation directory command. The filter characters
are:
* any character may follow ? any character in this position + the character in this position must be non-blank - the character in this position must be a blank / the character in this position must be numeric \ the character in this position must be non-numeric |
| Specify the Panvalet dataset name to be monitored | Enter the fully qualified name of the mainframe Panvalet dataset to be monitored. |
| Specify the optional type, with or without filter characters | If your installation has gone to the trouble of
setting up valid Panvalet types on the mainframe, then you can take
advantage of this information in selecting specific member types for you
monitor relationship. You may specify a specific type, or use filter
characters to be creative about a collection of types to be monitored.
The filter characters are imbedded with any other characters for pattern
matching of the Panvalet type, similar to the usage of the wildcard
characters on the workstation directory command. The filter characters
are:
* any character may follow ? any character in this position + the character in this position must be non-blank - the character in this position must be a blank / the character in this position must be numeric \ the character in this position must be non-numeric |
| Specify the environment | Enter the Endevor environment to be monitored. |
| System | Enter the Endevor system to be monitored. |
| Subsystem | Enter the Endevor sub-system to be monitored. |
| Specify the type | Endevor the specific Endevor type to be monitored. |
| Specify the CCID | If your environment requires a change control ID to be provided, then enter it here. |
| Specify the comment | If your environment requires a comment to be provided, or if you desire one, then enter it here. |
| Specify the LCM dataset name to be monitored | Enter the fully qualified name of the mainframe LCM dataset to be monitored. |
| Specify the system | Specify the LCM system to be monitored. |
| Specify the configuration | Specify the LCM configuration that is related to the LCM system to be monitored. |
| Specify the type | Specify the LCM type to be monitored. |
| Specify the sequential dataset name to be monitored | Enter the fully qualified name of the mainframe QSAM dataset to be monitored. |
| Specify the VSAM dataset name to be monitored | Enter the fully qualified name of the mainframe VSAM dataset to be monitored. |
| Handle as a fixed length file | The resulting imported file will be converted to the proper MERANT format in fixed format, with the minimum record length set to the maximum record length. |
| Monitor for both upload and download | Monitor, and allow both uploads and downloads to occur. |
| Monitor for upload to the mainframe only | Monitor, but do not allow a download to occur. This will allow upload synchronization to occur. |
| Monitor for download to the workstation only | Monitor, but do not allow an upload to occur. This will allow download synchronization to occur. |
| Monitor, but do not upload or download | Monitor, but do not allow an upload or download to occur. This will produce a report only. |
| Optionally, monitor only for members matching this filter | You may specify a specific member name, or use filter
characters to be creative about a collection of members to be monitored.
The filter characters are imbedded with any other characters for pattern
matching of the member name, similar to the usage of the wildcard
characters on the workstation directory command. The filter characters
are:
* any character may follow ? any character in this position + the character in this position must be non-blank - the character in this position must be a blank / the character in this position must be numeric \ the character in this position must be non-numeric |
| Location of workstation directory | You must specify the fully qualified location of a workstation directory to complete the monitor relationship. This is the name of the directory without any additional characters such as *.CBL. You may use the browse button to aid in the location of the directory. |
| Location of PVCS archive | You must specify the fully qualified location of a PVCS archive CFG file to complete the monitor relationship. This is the name of the archive with the usual ARCHIVENAME.CFG at the end. You may use the browse button to aid in the location of the archive file. |
| Extension | You must specify the specific extension, such as all CBL files in the directory, to be monitored against, or written as. |
| Monitor against | Select whether you are monitoring against a directory of standard files, or a PVCS archive. |
| Optional version label | If you are monitoring against PVCS, then you may monitor against a specific version label, if desired. |
| Optional promotion group | If you are monitoring against PVCS, then you may monitor against a specific promotion group, if desired. |
The Compare and Synchronize Monitor allows users to interrogate both workstation and mainframe source code and data files, and determine if any changes have occurred. If changes have occurred, then the user through configuration information, instructs the Monitor on the automatic action to be taken, such as downloading or uploading the change files. This enables an environment to be set up that allows a user to mirror workstation and mainframe files, and to automatically transport all changes to the mirrored counterpart.
To use the Compare and Synchronize Monitor, the user must perform a configuration. This is done in the MFMONMX program by using the Configure Options pull-down. This pull-down invoked the GUI configuration utility where the user instructs the Monitor on the workstation locations and mainframe datasets to be mirrored.
The Compare and Synchronize Monitor is useful for creating a local workstation directory that is identical to the mainframe datasets. This is helpful when using other products such as Mainframe Express, or Revolve, as the access to the workstation files is always faster than going over a communications link to any mainframe.
Copyright © 1999 MERANT International Limited. All rights reserved.
This document and the proprietary marks and names
used herein are protected by international law.
| SourceConnect for Mainframe Express and Revolve | Status Codes and Error Messages | |