This chapter describes how to configure Mainframe Access and verify that it is correctly installed and configured and is ready to run.
Following the instructions on the CD, you should have already completed the upload and restore of the Mainframe Access data sets. During that process you selected a high level qualifier to be used for all of your Mainframe Access data sets. This guide refers to the qualifier that you selected as <hlq> or hlq. The data sets that you restored are listed in the following table.
| DATA SET | DESCRIPTION |
|---|---|
| <hlq>.CNTL | Samples for Mainframe Access server. These include JCL for jobs to be run, JCL for started task procedures and parameter files. The members in this data set are referred to frequently in these configuration instructions. |
| <hlq>.LOADLIB | The load module library for Mainframe Access server. This library must be APF-authorized. |
| <hlq>.MFAVCTL | A pre-allocated library for Mainframe Access Data Connect server dynamic allocation control file members. This data set is allocated during installation but no members are restored into it. You may use this data set during customization for the Data Connect feature. |
| <hlq>.RIMS | All of the product source and object files that you may need during setup of the Remote IMS Server feature. |
| <hlq>.SASC.LINKLIB | The load module library for SAS/C runtime programs used by Mainframe Access server. This library must be APF-authorized. |
| <hlq>.TABLES | Translation tables used by Mainframe Access server. |
| <hlq>.WEBROOT.CLASS | Classes used by Mainframe Access web administration. |
| <hlq>.WEBROOT.GIF | Images used by Mainframe Access web administration. |
| <hlq>.WEBROOT.HTML | Pages used by Mainframe Access web administration. |
| <hlq>.WEBROOT.PUBLIC.HTML | Pages used by Mainframe Access web administration. |
The installation procedure places many samples in the <hlq>.CNTL data set. If a sample is provided for a configuration task, use it as a starting point for your configuration. Usually you need to edit the sample, replacing provided information with information that is unique to your system.
The following table summarizes the samples that are provided for Mainframe Access.
| MEMBER | DESCRIPTION |
|---|---|
| ACCESS | List used to restrict access to Mainframe Access consisting of the IP addresses of connecting clients. The access list also contains the list of user IDs that are authorized to access the Mainframe Access administration functions through the Web browser interface. You should add the IP addresses and user IDs for your system; see the section Editing Access List Definitions. |
| AUDIT | JCL for creating and initializing a Mainframe Access audit log data set. The audit log is a VSAM key sequenced data set (KSDS). You should edit the sample to include JOB card information, data set names and a volume serial number. |
| AUDRPT | JCL for running the Mainframe Access audit log report program to list the contents of the audit log data set. You should edit the sample to include JOB card information and data set names. |
| FRESTORE | A copy of the FRESTORE job for reference purposes. This job was originally transferred from CD to the <hlq>.UPLOAD data set during installation. The job was customized and submitted to allocate the permanent Mainframe Access data sets and restore the data set content from other uploaded files. |
| GTFCNTL | Input control statements referenced by the sample JCL procedure in member MFAGTF. |
| INSTALL | A copy of the installation upload instructions for reference purposes. These are the instructions that describe how to allocate the <hlq>.UPLOAD data set and transfer the CD content into that data set. |
| MFA | JCL for executing Mainframe Access. You should edit the sample to include your data set names. This JCL contains references to the ACCESS, PARMS and SERVERS sample members. |
| MFAAS | JCL for executing a Mainframe Access Application Server. Application servers are auxiliary address spaces that process specific types of client requests such as Endevor and SOA Express transactions. You should edit the sample to include your data set names. This JCL contains a reference to the PARMSAS sample member. |
| MFAGTF | JCL for running IBM's Generalized Trace Facility (GTF). GTF provides high-performance recording of diagnostic data and can be useful during problem determination. You should edit the sample to include your data set names. |
| MFANLS | JCL for re-compiling the default code page that may be configured at a client workstation. This is equivalent to the MFLSCTRN load module of Mainframe Access Version 2. During installation the default is set to use code pages E037/A437 for EBCDIC/ASCII translation. The sample JCL contains instructions for changing the default code pages selected by installation. |
| MFAS | JCL for executing the Mainframe Access Data Connect server. You should edit the sample to include your data set names. |
| MFAVTAM | Definition of VTAM applications for Mainframe Access, Mainframe Access Data Connect, ES/MTO and Remote IMS Server. You can edit the sample to include your own ACB names and network names (see the section VTAMLST Definitions). |
| PARMS | Parameters that are read when Mainframe Access is initialized. The sample JCL for executing Mainframe Access refers to this member for parameter input. You will need to edit some of these parameters. For full details see the section Editing Mainframe Access Parameters . |
| PARMSAS | Parameters that are read when a Mainframe Access Application Server address space initializes. The sample JCL MFAAS, for executing a Mainframe Access Application Server, refers to this member for parameter input. You will need to edit some of these parameters. For full details see the section Editing Mainframe Access Parameters . |
| PVSUFFX | JCL for executing a migration tool which extracts a text definition from the MFLSCPAN load module of Mainframe Access Version 2. For full details see the section Panvalet in Appendix C. |
| SERVERS | Definitions that describe the z/OS subsystems that will be providing service in response to client requests. The servers are your IMS and CICS subsystems, the Mainframe Access Data Connect server and ES/MTO servers. The clients include Mainframe Express, Mainframe Access client, Net Express, Revolve Enterprise Edition, and SOA Express requesters. You must edit the sample to include information specific to your servers and also coordinate the information with definitions in the client packages. |
| TSOXMIT | Sample job that uses TSO XMIT to package diagnostic data for transmission. |
| UPQUICK | A copy of the quick configuration instructions for reference purposes. These are the instructions that describe how to quickly configure z/OS and Mainframe Access to create an operational Mainframe Access server system. These same instructions are reiterated in the Quick Configuration section. |
There are two types of configuration tasks that you must complete before you can start and use Mainframe Access. These are:
The process of configuring Mainframe Access is separated into two distinct procedures; Quick Configuration and Advanced Configuration Activities.
Quick configuration is performed using the UpQuick instructions as indicated during the CD installation process. These configuration steps must be completed for all installations. Quick configuration takes care of all of the z/OS customizations and many basic Mainframe Access customizations. This quick configuration is the only mainframe Mainframe Access setup required for Mainframe Access Drag and Drop, SQL Option for DB2, Mainframe Access Web Administration and basic Mainframe Access Data Connect server functions.
Additional setup is required if you will be using Mainframe Access Data Connect server and you need to use the file name mapping table and/or alter the processing in the SAF security exits. Additional setup is also required if you will be using Remote IMS, CICS Option, SOA Express IMS support, ES/MTO support, Mainframe Access's access list checking, Mainframe Access's audit log, and/or Mainframe Access's support for external library management systems. The section on advanced configuration describes these additional customizations.
If you have completed the installation process, including the UpQuick configuration steps, and if you are not going to use features that require additional setup, your configuration is complete.
If you have uploaded and restored the Mainframe Access data sets but you have not completed the UpQuick configuration, you should begin with Quick Configuration.
If you have completed the configuration and testing of your basic Mainframe Access server and you need to customize for an advanced feature, you should continue at Advanced Configuration Activities.
After you have uploaded the mainframe files and successfully run the FRESTORE job, there are some basic customization tasks that must be completed. Quick configuration works through these configuration tasks quickly and gets you to the point where the software can be started and a basic installation verification check can be performed. After the installation verification check, continue with Advanced Configuration Activities if there are additional features that you need to set up.
You should be familiar with TSO, ISPF, SDSF, z/OS system commands, JCL procedures and proclibs, VTAMLST definitions and RACF.
Note: These instructions refer to RACF as the security subsystem. Mainframe Access does use the SAF interface to the security subsystem and is compatible with other security products that provide the SAF API. When these instructions refer to RACF-related customizations, please refer to your security product documentation to determine the corresponding security subsystem changes.
If you are using the ISPF editor to make the configuration changes, use the change command once to make the first update to the hlq value and then use ISPF's Rchange command (usually PF6) to apply the same change in all the members that you need to update. For example: use "c HLQ MY.HIGH.LEVEL" the first time and then PF6 to apply the same change in other places. Changes to other parameters are easily accomplished by overtyping the preset value.
The following table lists important configuration data that you will need to know in order to complete the quick configuration. Review these items and determine the appropriate values before you proceed with customization.
| ITEM | DESCRIPTION |
|---|---|
| userid | TSO user ID that can update proclib, update vtamlst, update RACF, and issue z/OS system commands through SDSF. Alternatively, the cooperation of individuals with the appropriate authorities. |
| hlq | High level qualifier that was given to all Mainframe Access data sets when the FRESTORE job was run. |
| clientport | A TCP/IP port number on the mainframe that you will reserve for Mainframe Access and client connections. |
| adminport | A TCP/IP port number on the mainframe that you will reserve for Mainframe Access Web Administration connections from web browsers. |
| stcuserid | RACF user ID that you want to associate with the Mainframe Access started tasks |
| stcgroup | RACF group ID that you want to associate with the Mainframe Access started tasks. |
| tcpdata | Data set name of the IBM TCP/IP "TCPIP.DATA" data set that provides configuration information to programs that use TCP/IP. This data set is not need if you are using CA TCPaccess. |
| proclib | Data set name of a system procedure library. |
| vtamlst | Data set name of the active VTAMLST definitions data set. |
| netid | VTAM SNA network id used on your system. See NETID= in the active ATCSTRxx vtamlst member. |
| loadvolser | DASD volume serial number of the volume containing the Mainframe Access load module libraries and the SAS/C runtime library. FRESTORE allocated and built these libraries. |
Customize member ACCESS in the CNTL data set. Change ADMUSER=MFAUSER to ADMUSER=userid. This will allow userid to log on to Mainframe Access Web Administration. The ADMUSER= line can also be repeated to add additional userids.
Customize member MFA in the CNTL data set. This is the started task JCL procedure for Mainframe Access server. Use the ISPF change command to change HLQ to your qualifier (hlq).
If you are using IBM's TCP/IP, overtype TCPIP.OS390.TCPDATA with the name of your installation's "TCPIP.DATA" data set (tcpdata). This is the data set used by client programs to obtain the name of the TCP/IP started task and other installation-dependent TCP/IP information.
Customize member MFAAS in the CNTL data set. This is the started task JCL procedure for Mainframe Access Application Servers. Use the ISPF change command to change HLQ to your qualifier (hlq).
If you are using IBM's TCP/IP, overtype TCPIP.OS390.TCPDATA with the name of your installation's "TCPIP.DATA" data set (tcpdata).
Customize member MFAS in the CNTL data set. This is the started task JCL procedure for Mainframe Access Data Connect server. Use the ISPF Rchange command to change HLQ to your qualifier (hlq).
Customize member PARMS in the CNTL data set. These are the Mainframe Access server initialization parameters referenced by the Mainframe Access started task JCL.
Use the ISPF Rchange command to change HLQ to your qualifier (hlq) in the WEB_ROOT=HLQ.WEBROOT parameter. This parameter specifies the prefix for data sets used by the Mainframe Access web server feature.
Change TCP_PORT=2020 to TCP_PORT=clientport. This is the port number that Micro Focus client software should be configured to use.
Change ADMIN_PORT=2021 to ADMIN_PORT=adminport. This is the port number that a web browser should use to access Web Administration.
Change NETWORK ID=DDINET1 to NETWORK ID=netid, the VTAM SNA network id of your system.
If you are using CA TCPaccess, change TCPACCESS=NO to TCPACCESS=YES to select Mainframe Access server's interface to TCPaccess.
Copy member MFAVTAM to vtamlst. This application major node definition contains APPL definitions for Mainframe Access server, Mainframe Access Data Connect server and Remote IMS Server. Use the z/OS VARY command to activate the definition:
V NET,ACT,ID=MFAVTAM
Notes:
Copy members MFA, MFAAS and MFAS to proclib.
Notes:
Use z/OS SETPROG commands to APF-authorize the load libraries:
SETPROG APF,ADD,DSNAME=hlq.LOADLIB,VOLUME=loadvolser SETPROG APF,ADD,DSNAME=hlq.SASC.LINKLIB,VOLUME=loadvolser
Note: You will want to add these APF library definitions to a SYS1.PARMLIB(PROGxx) member so that these same authorizations are automatically activated during z/OS system initialization.
Use RACF TSO commands to define the Mainframe Access started tasks (MFA, MFAAS and MFAS) and assign a userid and groupid to the tasks. The stcuserid should have appropriate access to the Mainframe Access data sets and should also have a basic OMVS RACF segment defined. At a minimum, the stcuserid OMVS segment must have a UID. The stcgroup must also have an OMVS segment with a GID. The following REDEFINE will provide the necessary definition for all of the started tasks (MFA, MFAAS and MFAS).
RDEFINE STARTED MFA*.* STDATA(USER(stcuserid) GROUP(stcgroup)) OWNER(stcuserid) SETROPTS RACLIST(STARTED) REFRESH
If you are using another security product such as CA-ACF2 or CA-Top Secret you will need to make similar updates to your security system definitions. MFA, MFAAS and MFAS will need a started task definition with an OMVS segment and they will need access to the SAF API for security subsystem calls. Please refer to your security product documentation.
When you have completed all of the tasks described in the preceding sections you are ready to start Mainframe Access to perform some simple installation verification tests. Start Mainframe Access by issuing the following z/OS START command at a system console or using the TSO/ISPF SDSF command facility:
S MFA
Here is an example that shows the messages displayed during startup. The start command is issued for MFA, the name of the started task JCL sample that has been customized and copied into a system procedure library. The SERVERS sample also defines the Mainframe Access Data Connect server as an application server address space that should be started automatically by Mainframe Access during initialization. Mainframe Access issues an internal start command for MFAS, the name of the started task JCL sample for the Mainframe Access Data Connect server.
15:49:32.45 CSIRLW1 00000290 S MFA
15:49:32.47 STC05579 00000090 $HASP100 MFA ON STCINRDR
15:49:32.55 STC05579 00000290 IEF695I START MFA WITH JOBNAME MFA IS ASSIGNED TO USER RWITEK, GROUP DEVELOP
15:49:32.55 STC05579 00000090 $HASP373 MFA STARTED
15:49:32.55 STC05579 00000090 IEF403I MFA - STARTED - TIME=15.49.32
15:49:32.85 STC05579 00000090 MFM0014I: Mainframe Access V3.10 (BASE) for YOUR_COMPANY_NAME
15:49:32.85 STC05579 00000090 MFM0066I: Address space type is CTLRGN
15:49:32.86 STC05579 00000090 MFM0057I: GTF user record id (eid) is 00E9
15:49:32.86 STC05579 00000090 MFM0012I: TCP port number is 1503
15:49:32.86 STC05579 00000090 MFM0013I: Admin port number is 1504
15:49:32.86 STC05579 00000090 MFM0047I: DSS maximum shared public files is 10
15:49:32.86 STC05579 00000090 MFM0055I: DSS scan interval is 30 minutes
15:49:32.86 STC05579 00000090 MFM0054I: SMF recording is off, record id is zero or invalid
15:49:32.87 STC05579 00000090 MFM0063I: MFA Direct is active
15:49:32.87 STC05579 00000090 MFM0064I: MFA Direct number of processing tasks is 5
15:49:33.16 STC05579 00000090 MFMDS052I CA/PanValet Ready
15:49:33.21 STC05579 00000090 MFMDS055I MCG/RPC feature inactive
15:49:33.22 STC05579 00000090 MFMDS001I DSS Server Ready
15:49:36.92 STC05579 00000090 MFM0001I: Mainframe Access V3.10 (BASE) is active
15:49:37.00 STC05580 00000090 $HASP100 MFAS ON STCINRDR
15:49:37.06 STC05580 00000090 $HASP373 MFAS STARTED
15:49:37.06 STC05580 00000090 IEF403I MFAS - STARTED - TIME=15.49.37
15:49:37.23 STC05580 00000090 MFA302I.MFAS.MFDSTART / ATTACHING VTAM PROCESSOR
15:49:37.24 STC05580 00000090 MFA303I.MFAS.MFDSTART / MFA/DATACONNECT V3.10 BASE COPYRIGHT (C)
1987-2007 MICRO FOCUS INTERNATIONAL LTD.
15:49:37.24 STC05580 00000090 MFA110I.MFAS.MFDFSQ00 / VTAM PROCESSOR ACTIVE USING VTAMAPPL MFA62ACB
A successful connection to the Mainframe Access Web Administration feature from a standard Web browser program verifies that basic client connectivity through the TCP/IP network is functioning correctly. Specify the URL to the Web browser as
http://your.mainframe.hostname:adminport
where your.mainframe.hostname is the TCP/IP hostname or IP address for the z/OS system where Mainframe Access is executing and adminport is the port number that you specified in the Mainframe Access parameters. The administration port number is also identified in the Mainframe Access startup messages.
When you successfully connect, you will receive the Mainframe Access Web Administration sign-on page. Type your userid and password and press login to access the Web Administration home page. No explicit logout is necessary when you wish to leave Web Administration.
Stop Mainframe Access by issuing the following z/OS STOP command at a system console or using the TSO/ISPF SDSF command facility:
P MFA
Here is an example that shows the messages displayed during shutdown. The stop command is issued only for Mainframe Access, the Mainframe Access server. Mainframe Access issues an internal stop command for MFAS, the application server address space for Mainframe Access Data Connect that was defined in the SERVERS member and started automatically by Mainframe Access. MFAS ends first and then Mainframe Access completes its shutdown processing.
16:44:18.52 CSIRLW1 00000290 P MFA 16:44:21.52 STC05579 00000290 P MFAS 16:44:21.53 STC05580 00000090 MFA112I.MFAS.MFAFSQ00 / VTAM PROCESSOR HAS TERMINATED 16:44:21.68 STC05580 00000090 MFA317I.MFAS.MFARSC00 / HAS BEEN TERMINATED 16:44:21.69 STC05579 00000090 MFMDS005I DSS Server shutdown 16:44:21.70 STC05580 00000090 IEF404I MFAS - ENDED - TIME=16.44.21 16:44:21.70 STC05580 00000090 $HASP395 MFAS ENDED 16:44:32.77 STC05579 00000090 MFM0011I: Mainframe Access shutdown completed 16:44:32.82 STC05579 00000090 IEF404I MFA - ENDED - TIME=16.44.32 16:44:32.82 STC05579 00000090 $HASP395 MFA ENDED
Mainframe Access is a general purpose server supporting a variety of Micro Focus client products. The Quick Configuration process that you have completed enables a large number of Mainframe Access server features that will satisfy most access requirements for Net Express, Revolve Enterprise Edition, Mainframe Access client and SQL Option for DB2. This section describes the customizations (beyond the quick configuration) that are needed to enable various additional features of Mainframe Access server.
The following table summarizes the required updates on a per-feature basis. This will help you to select the correct configuration activities for a specific feature.
| Feature | Customization |
|---|---|
| Audit Log | Refer to Allocating and Initializing an Audit Log Data Set to prepare the data set. Then see Editing Mainframe Access Parameters and update the audit log parameter to AUDIT LOG=YES. |
| Access List | Refer to Editing Access List Definitions for guidance in defining IP addresses and address ranges. Then see Editing Mainframe Access Parameters and update the access list check parameter to ACCESS LIST CHECK=YES. |
| CICS Option | Using CICS Option, Mainframe Express clients can
interact with z/OS CICS servers for file access, remote program execution,
transaction execution, etc. Refer to
Editing Mainframe Access Server
Definitions for guidance in defining a z/OS CICS
server to Mainframe Access. Then see
Editing Mainframe Access
Parameters and activate support for this feature by
setting MCO FEATURE=YES and setting
MCOLINK_MAXTASKS=2. The number of tasks supporting this
feature can be increased in the future as your usage dictates.
To complete the setup for this feature you will need to customize your Mainframe Express client and the z/OS CICS server. |
| Remote IMS Option | Using the Remote IMS Option, Mainframe Express clients
can execute DL/I calls that are processed by a z/OS IMS server. Refer to
Editing Mainframe Access Server
Definitions for guidance in defining a z/OS IMS server
to Mainframe Access. Then see
Editing Mainframe Access
Parameters and activate support for this feature by
setting REMOTE IMS FEATURE=YES and setting
IMSLINK_MAXTASKS=2. The number of tasks supporting this
feature can be increased in the future as your usage dictates.
To complete the setup for this feature you will need to customize your Mainframe Express client and the z/OS IMS server. You must also install the Remote IMS server software in the target z/OS IMS server and enable APPC/MVS communications for that IMS server. All of the machine-readable installation materials for your Remote IMS Server can be found in the <hlq>.RIMS data set. |
| List DB2 | Mainframe Access' List DB2 feature dynamically identifies z/OS DB2 and IMS servers that are active on the z/OS system where Mainframe Access server is executing. A summary of the server information can be viewed using the web administration interface. This information can be helpful when defining these systems to Mainframe Access server and Mainframe Express clients. Refer to Editing Mainframe Access Parameters and activate support for this feature by setting LIST DB2=YES . |
| Data Connect | Quick Configuration installs the Mainframe Access Data Connect server with SAF security checking active and without special customizations for PC to mainframe file name mapping. If you need to alter this basic setup see the appendix Data Connect . |
| SOA Express IMS Support | Using SOA Express, client applications can
invoke z/OS IMS transactions and use the transaction output data for further
processing and/or end user displays. This feature communicates with client
applications through IBM MQ Series message queues. The client requests invoke
generated eBiz load modules that use the IMS OTMA interface to drive the target
IMS transaction and retrieve the transaction output data. Transaction output
data is returned to the requesting client in a MQ Series message. See the appendix
SOA Express IMS Support for guidance in defining Application
Server address spaces, defining MQ message queues for SOA Express IMS
processing and activating the MFA Server support for this feature.
To complete the setup for this feature, you need to customize your client software and the z/OS IMS server. See your SOA Express Configuration Guide and the IBM z/OS IMS publications for help with these customizations. |
| Enterprise Server/Mainframe Transaction Option Support | Enterprise Server/Mainframe Transaction Option (ES/MTO)
support enables Mainframe Access server to accept CICS ISC requests initiated by z/OS CICS and route them to an ES/MTO server for execution.
The combination of ES/MTO support and Mainframe Express's CICS Option support creates a bi-directional ISC connection between ES/MTO and z/OS CICS.
See the appendix Enterprise Server/Mainframe Transaction Option Support for guidance in defining ES/MTO servers, z/OS CICS
servers, and activating the MFA Server support for this feature.
To complete the setup for this feature you need to customize your ES/MTO server(s) and the z/OS CICS server(s). See your Enterprise Server documentation and IBM z/OS CICS publications for help with these customizations. |
| ChangeMan interface | Mainframe Access' Source Connect feature works with ChangeMan to provide client access to ChangeMan-managed files. For more information see the section ChangeMan ZMF in the appendix External Library Management Systems . |
| Panvalet interface | Mainframe Access' Source Connect feature works with Panvalet to provide client access to Panvalet-managed files. For more information see the section Panvalet in the appendix External Library Management Systems . |
| Librarian interface | Mainframe Access' Source Connect feature works with Librarian to provide client access to Librarian-managed files. For more information see the section Librarian in the appendix External Library Management Systems . |
| Endevor interface | Mainframe Access' Source Connect feature works with Endevor to provide client access to Endevor-managed files. For more information see the section Endevor in the appendix External Library Management Systems . |
Note: As noted in the preceding customization summaries, you also need to prepare the external servers and clients that Mainframe Access works with. For details of where to find information on the preparation tasks, see the section Configuring the Associated Clients and Products in the chapter Introduction.
You edit the Mainframe Access parameter definitions located in member PARMS to customize them for your system. The sample parameter definitions are provided here as a convenient reference while you read. Lines that begin with an asterisk are treated as comments and are skipped in processing. All parameters must be contained on a single input statement and we recommend that you begin your parameter keywords in column 1. The first blank character following a parameter value indicates the end of the parameter keyword and value pair and any text following that blank is treated as a comment.
*--------------------------------------------------------------------*
* *
* Micro Focus Mainframe Access - Initialization Parameters *
* *
* For minimum customization during installation you should review *
* the following parameters and change them to suit your *
* installation, if necessary. These customizations will allow you *
* to complete the installation and perform basic installation *
* verification testing. These minimum customizations are also *
* sufficient to enable testing of MFA and MFE SQL Option client *
* functions. *
* *
* TCP_PORT port to be used by client applications *
* ADMIN_PORT port to be used for web administration (browser) *
* WEB_ROOT change HLQ *
* to the value selected during installation *
* NETWORK ID see VTAM definitions in SYS1.VTAMLST(ACTSTRxx) *
* LU62 APPLID update if you changed sample MFAVTAM *
* APPLID PASSWORD update if you changed sample MFAVTAM *
* TCPACCESS specify YES if you are using CA TCPAccess *
* *
* Additional customization and/or setup work is required to enable *
* the use of other product functions. After installation *
* verification testing, refer to the product documentation to *
* continue with customization for these additional functions: *
* *
* MFE CICS Option *
* MFE IMS Option *
* MFA access list checking *
* MFA audit logging *
* MFA support for external library managers *
* SOA Express IMS support *
* ES/MTO *
* *
* *
* Change Log *
* *
* *
* ChangeID Description *
* -------- -------------------------------------------------------- *
* SP2 New parameter - BIND_NETADDR=0.0.0.0 *
* SP2 New parameter - MFA_MCG_DB2CONNECTION=RRSAF *
* SP2 New parameter - CHANGEMAN_SSID= *
* SP2 New parameter - CHANGEMAN_ASGROUP=CGMQ *
* SP2 New parameter - CHANGEMAN_INTERFACE=SERXMLAC *
* SP2 New parameter - CHANGEMAN_DSNQUALIFIER= *
* WS05HF1 New parameter - CHANGEMAN_COMMON_BUILD=NO *
* WS05HF1 New parameter - CHANGEMAN_TEST_OPTION=NO *
* WS05HF1 New parameter - MFA_ENDEVOR_INTERFACE=YES *
* WS05HF1 New parameter - MFA_PANVALET_INTERFACE=YES *
* WS05HF1 New parameter - MFA_LIBRARIAN_INTERFACE=YES *
* WS05HF1 New parameter - MFA_LIBRARIAN_DIR_INFO=LONG *
* WS06 New parameter - ES/MTO OUTBOUND FEATURE=NO *
* WS06 ChangeMan parameters moved to MFA services section *
*--------------------------------------------------------------------*
*
*--------------------------------------------------------------------*
* General Parameters *
*--------------------------------------------------------------------*
*
SYSOUT=A --- Required if TRACE=SYSPRINT
ROUTE=(2,11) --- Console message route codes
ORGANIZATION=YOUR_COMPANY_NAME --- Company name (no embedded spaces)
ASTYPE=CTLRGN --- Parms for MFA control region
NETWORK ID=DDINET1 --- SNA network ID where MFA is running
LU62 APPLID=MFM62ACB --- VTAM LU6.2 APPL
APPLID PASSWORD=MFM62PSW --- VTAM LU6.2 APPL password
TRACE=SYSPRINT --- "SYSPRINT", "GTF" or "CONSOLE"
TRACING=NO --- Start tracing (YES/NO)
LIST PARMS=YES --- List parameters on sysout (YES/NO)
EID=00E9 --- Required if TRACE=GTF
COMPRESSION=NO --- Compression for SQL Option traffic
ACCESS LIST CHECK=NO --- Access List checking (YES/NO)
AUDIT LOG=NO --- Audit Logging (YES/NO)
TCP_PORT=2020 --- TcpIp port for MFE, MFA, TELNET
ADMIN_PORT=2021 --- TcpIp port for Web Server
BACKLOG=5 --- TcpIp "listen" backlog
BUFFER SIZE=0 --- TcpIp send/recv buffer size (0=MAX)
TIME OUT FOR CONNECTION=30 --- TcpIp idle timeout minutes (0=NONE)
TIME OUT FOR INITIAL RECV=10 --- Initial recv tot seconds (1<x<59)
MAX_PUBLIC_FILES=10 --- Dataset Services max shared files
DSS_SCAN_INTERVAL=30 --- Dataset Services scan interval
SMF_RECORDID=0 --- SMF record ID
TCPACCESS=NO --- NO=IBM TCP/IP; YES=CA TCPACCESS
CGMQOTMA LOGDD=SYSOUT --- CG production log DDname or "SYSOUT"
BIND_NETADDR=0.0.0.0 --- Hostname/IP address for listeners
WEB_ROOT=HLQ.WEBROOT
*
*--------------------------------------------------------------------*
* Mainframe Access services parameters *
*--------------------------------------------------------------------*
*
MFA_ENDEVOR_INTERFACE=YES --- Use Endevor interface (YES,NO)
MFA_PANVALET_INTERFACE=YES --- Use Panvalet interface (YES,NO)
MFA_LIBRARIAN_INTERFACE=YES --- Use Librarian interface (YES,NO)
MFA_ENDEVOR_HISTORY=YES --- Endevor MFALOGE history (YES,NO)
MFA_LIBRARIAN_HISTORY=YES --- Librarian MFALOG history (YES,NO)
MFA_LIBRARIAN_UPD_MODULE=AFOLIBR - Librarian batch update module name
MFA_LIBRARIAN_DIR_INFO=LONG --- Librarian dir list (SHORT or LONG)
MFA_PANVALET_HISTORY=YES --- Panvalet MFALOG history (YES,NO)
MFA_PANVALET_UPD_MODULE=PAN#1 --- Panvalet batch update module name
MFA_SAF_HISTORY=YES --- Data set access MFALOG history
MFA_SYSOUT_CLASS=A --- MFALOG,MFALOGE,SNAPDUMP class
MFA_SYSOUT_DEST=LOCAL --- MFALOG,MFALOGE,SNAPDUMP dest
MFA_MCG_DB2CONNECTION=RRSAF --- MCG DB2 connection (CAF or RRSAF)
CHANGEMAN_SSID= --- ChangeMan subsystem ID x ("SERx")
CHANGEMAN_ASGROUP=CGMQ --- ChangeMan address space group name
CHANGEMAN_INTERFACE=SERXMLAC --- ChangeMan XML batch client interface
CHANGEMAN_DSNQUALIFIER= --- ChangeMan DSN qualifier
CHANGEMAN_COMMON_BUILD=NO --- ChangeMan shared build opts (YES/NO)
CHANGEMAN_TEST_OPTION=NO --- ChangeMan <TEST> option (YES/NO)
*
*--------------------------------------------------------------------*
* Services to be activated *
*--------------------------------------------------------------------*
*
TCP LINK FEATURE=YES --- MFE SQL Option, Telnet client
MFADIRECT=YES --- Mainframe Access services
MFA FEATURE=YES --- Mainframe Access Data Connect Server
PEM FEATURE=YES --- MFE Password Expiration Manager
MCO FEATURE=NO --- MFE CICS Option
REMOTE IMS FEATURE=NO --- MFE IMS Option
CGMQOTMA FEATURE=NO --- SOA Express IMS support
LIST DB2=NO --- DB2 and IMS subsystem finder
ES/MTO OUTBOUND FEATURE=NO --- ES/MTO Outbound support
*
*--------------------------------------------------------------------*
* Number of tasks to run for each service *
*--------------------------------------------------------------------*
*
TCPLINK_MAXTASKS=2 --- # of TCBS for TCP LINK feature
WWWS_MAXTASKS=2 --- # of TCBS for Web Server
ISPI_MAXTASKS=2 --- # of TCBS for Web Server ISPI pgms
MFALINK_MAXTASKS=2 --- # of TCBS for MFA Server routing
MFADIRECT_MAXTASKS=5 --- # of TCBS for MFA processing
IMSLINK_MAXTASKS=0 --- # of TCBS for MFE IMS Option
MCOLINK_MAXTASKS=0 --- # of TCBS for MFE CICS Option
*
END
The order shown here is a logical one. However, you can enter the parameters in any order, as long as they are followed by the END marker. We strongly recommend that the SYSOUT and ROUTE parameters be specified at the beginning of the definitions to ensure that startup messages issued during the remainder of parameter processing reach the proper destinations. The following table lists and describes the parameters in alphabetical order.
| Parameter | Description |
|---|---|
| ACCESS LIST CHECK1 | Indicates whether or not the access list feature is to be activated for clients. This enables you to restrict access to Mainframe Access according to the connecting client's IP address (see the section Editing Access List Definitions). Specify NO to accept all client connection requests, regardless of the client's IP address. Specify YES to permit client connections based on the PERMIT and REJECT rules for IP addresses defined in your access list. |
| ADMIN_PORT | The port number that accepts connections from HTTP clients, including Web Administration clients. The specified port number must be reserved for use by Mainframe Access. You can explicitly reserve the port for Mainframe Access by updating the MVS TCP/IP profile data set. If the specified port is not available during Mainframe Access startup, startup will fail. Specify any valid TCP/IP port number. |
| APPLID PASSWORD | The ACF/VTAM ACB password to be used when Mainframe Access opens its VTAM ACB. Specify a password consisting of between one and eight characters. This value must match the password value specified by the PRTCT parameter in the Mainframe Access VTAM application program major node definition in VTAMLST. |
| ASTYPE | Specifies the type of Mainframe Access server region.
Valid values are CTLRGN, STANDARD and APPSERVER:
|
| AUDIT LOG | Indicates whether or not the audit log is to be activated. Specify YES to activate or NO to deactivate. If audit logging is selected, be sure to complete the tasks described in the section Allocating and Initializing an Audit Log Data Set, above. |
| BACKLOG | The number of pending TCP/IP connection requests that the TCP/IP network software should hold while Mainframe Access is processing the current connection request. Connection processing is typically handled very quickly and a small backlog of between 5 and 10 should be adequate for most installations. If you have an unusually high number of concurrent connection requests, some end users might receive a connection reject message. Specify a positive integer value in the range 5 through 50. |
| BIND_NETADDR | Selects the network address(es) to which the Mainframe Access listening ports (TCP_PORT and ADMIN_PORT) should be bound. Specify 0.0.0.0 (or omit this parameter) to bind the ports to all network addresses assigned to the host system. Specify a specific network address or a logical host name (64-character maximum) to restrict Mainframe Access to a single, specific host network address. |
| BUFFER SIZE | The maximum amount of data that Mainframe Access should send or receive through the TCP/IP network software in one send or receive operation. Specify 0 (zero) to allow Mainframe Access to use the optimum buffer size; this is recommended, as it will reduce the number of send or receive calls made to the TCP/IP network software. Specify an explicit value in the range 512 to 32767 only if you have diagnosed a problem with your TCP/IP network software that is associated with large message sizes. |
| CGMQOTMA FEATURE | Indicates whether or not communication with IMS subsystems used by SOA Express IMS support is to be activated. SOA Express uses IBM MQ Series messaging to communicate with clients and IBM IMS OTMA calls to communicate with the target IMS system. Specify YES to activate the SOA Express IMS support feature or NO to deactivate it. |
| CGMQOTMA LOGDD | Specifies the destination for the SOA Express IMS support production log messages. The default value of SYSOUT is appropriate for most installations and causes the production log messages to be written to the Mainframe Access Server XDBOUT data set. A pre-allocated DASD data set can be used for the production log by adding a DD statement for the data set to the Mainframe Access Server started task JCL (see the MFA sample member) and then specifying the statement's DD name in this parameter. If a production log data set operation (OPEN or WRITE) fails, the messages are automatically redirected to the XDBOUT data set. |
| CHANGEMAN_ASGROUP | Specifies
the name of the MFA Server address space group used to process all
ChangeMan requests. The SERVERS sample defines an address space group named
CGMQ that is shared by ChangeMan definitions and SOA Express IMS
definitions. If you use both features of MFA Server it is possible,
but not necessary, to create separate ASGROUP definitions.
The ASGROUP definition in the SERVERS member names a JCL procedure used to initiate the dependent region started tasks. MFA Server provides a procedure named MFAAS that serves as the basis for all dependent-region JCL procedures. You customize and add this JCL to a system procedure library during server installation. Some features of the MFAAS JCL procedure appear as JCL comment statements that you can customize yourself, including symbolic parameters and STEPLIB program library names. You can also customize any of several specialized ChangeMan DD statements in the procedure. The MFAAS JCL contains text that explains all required customizations for ChangeMan. Specify the one- to four-character ASGROUP name to associate with ChangeMan processing. If you omit this parameter the address space group name defaults to CALL. |
| CHANGEMAN_COMMON_BUILD | Specifies whether or not Mainframe Access accommodates group builds submitted under AppMaster Builder. Specify YES to enable group builds or NO to disable them. The default is NO. When enabled for group builds, MFA modifies the build options for each member of the AMB group to match the component name and type submitted, ensuring that each build request in the group is properly executed. |
| CHANGEMAN_DSNQUALIFIER | Specifies a high-level qualifier for dynamically allocated data sets created by MFA Server to hold input files during the staging process. MFA Server
creates these data sets dynamically as card-image sequential data sets that are deleted when the associated client request completes. The default qualifier is the login ID of the
current user. You should set an alternate qualifier if your installation’s SERNET does not have RACF authority to read or write data into files stored in data sets named with the
current user’s login ID as the high-level qualifier.
If an alternate qualifier is required, see your ChangeMan administrator or your security administrator for assistance in selecting a proper value. If your ChangeMan functionality is restricted by security subsystem authorizations, you might need to specify your dataset high-level qualifier such that read access to the data sets is always permitted. |
| CHANGEMAN_INTERFACE | Specifies the name of the ChangeMan ZMF module. During ChangeMan request processing, MFA Server loads and branch enters this module. Valid values are
SERXMLBC and SERXMLAC. The default is SERXMLAC.
The preferred interface module is SERXMLAC, which is not documented by Serena; however, it provides better interface performance than SERXMLBC by using virtual storage instead of data sets for XML input and output exchange between MFA Server (the requester) and ChangeMan ZMF. Serena documents only the SERXMLBC interface, which is the XML services batch client. SERXMLBC is intended for use in a batch job stream and requires XMLIN and XMLOUT DD statements to define its required data sets. The MFAAS JCL sample provides sample DD statements for XMLIN and XMLOUT; however, they are commented out. If you must use SERXMLBC, contact SupportLine for assistance with data set definitions. This parameter is required in both the PARMS member and the PARMSAS member used by application server address spaces. |
| CHANGEMAN_SSID | Initializes the Mainframe Access ChangeMan interface by providing the final character of the z/OS subsystem ID used to identify ChangeMan. Omit this
parameter to bypass Mainframe Access initialization for the ChangeMan interface. Valid values are any single alphabetic or numeric character. The character specified is appended to the
subsystem ID string "SER", completing the four-character ID. For example, if you specify CHANGEMAN_SSID=A, the z/OS subsystem ID becomes "SERA".
This parameter is required in both the PARMS member and the PARMSAS member used by application server address spaces. Your ChangeMan administrator can help you to determine the correct subsystem ID to use. |
| CHANGEMAN_TEST_OPTION | Specify whether or not MFA uses the XML trace option. Specify YES to enable XML trace or NO to disable it. The default is NO. When enabled, SERNET logs information in XML format into the standard SERPRINT DD file. This file can be used to identify problems and to validate MFA services. Enabling XML trace is not recommended for production systems due to the large volume of log data generated. |
| COMPRESSION | Indicates whether or not Mainframe Access should apply data compression when communicating with SQL Option for DB2 clients. Specify YES to activate data compression or NO to deactivate it. |
| DSS_SCAN_INTERVAL | The time period in minutes between Data Set Services checks for abandoned buffers or open files. Due to unforeseen environmental errors, transactions may abnormally terminate while holding open files and other I/O resources. These scans locate idle resources and return them to an available status and ensure that no file is held idle for more than two consecutive scan intervals. Specify the number of minutes as an integer value between 30 and 90. The default is 30 minutes. |
| EID | The event ID of Mainframe Access GTF user trace records. The EID must be available for exclusive use by Mainframe Access and must match the USR=(eid) parameter specified to GTF when GTF is started (see the sample member GTFCNTL). This parameter is valid only when TRACE=GTF is specified. Specify a hexadecimal number of up to four bytes that GTF recognizes as a valid user trace record identifier. |
| ES/MTO OUTBOUND FEATURE | Controls whether or not Mainframe Access accommodates ES/MTO. Specify YES to enable
ES/MTO support or NO to disable it. The default is NO.
When disabled, MFA Server initialization ignores all ES/MTO server definitions contained in the SERVERS startup member. When enabled, MFA Server processes ES/MTO server definitions at startup, initializing and allocating the VTAM ACBs defined for ES/MTO support. MFA Server also starts the required processes to manage ISC conversations initiated by the defined z/OS CICS systems to the defined ES/MTO servers. |
| IMSLINK_MAXTASKS 2 | The number of z/OS subtasks (TCBs) to be started and dedicated to processing requests from IMS Option (Remote IMS) clients. Specify 0 (zero) or a positive integer value between 1 and 50. |
| ISPI_MAXTASKS 2 | The number of z/OS subtasks (TCBs) to be started and dedicated to processing HTTP requests to execute server-side programs performing Mainframe Access Web Administration. Web Administration uses the Mainframe Access Internet Server Programming Interface (ISPI) to analyze the various administrative requests received from Web browsers and create dynamic HTML responses. Specify a positive integer value between 1 and 50. |
| LIST DB2 | Indicates whether or not the Mainframe Access LIST DB2 feature is to be activated. This obtains information about the DB2 and IMS subsystems. Specify YES to activate LIST DB2 or NO to deactivate it. |
| LIST PARMS | Controls the listing of Mainframe Access parameter definitions on the XDBOUT sysout data set. The parameter listing is helpful when you need to examine the active configuration settings. Specify YES to echo parameter definitions to the XDBOUT sysout data set or NO to inhibit the listing. |
| LU62 APPLID 3 | The ACF/VTAM ACBNAME to be used by Mainframe Access. This ACBNAME must match the ACBNAME parameter of an active VTAM application major node (see the section Editing Mainframe Access Server Definitions). Mainframe Access issues a VTAM OPEN request for this ACBNAME during startup and initialization fails if the OPEN is not successful. This ACBNAME (or the possibly different "network name" specified in the VTAM application major node definition) is the SNA LU name that identifies Mainframe Access to other applications in your SNA network. Specify the ACBNAME that has been defined and activated for Mainframe Access. |
| MAX_PUBLIC_FILES | The maximum number of shared public files that Mainframe Access Data Set Services should keep available. When the maximum is reached the next request for a new public file will be rejected, and you must close one of the item libraries to make space for the new one. Specify an integer value between 24 and 64. Defaults to 32. |
| MCOLINK_MAXTASKS 2 | The number of z/OS subtasks (TCBs) to be started and dedicated to processing requests from CICS Option clients. Specify 0 (zero) or a positive integer value between 1 and 50. |
| MFADIRECT | Indicates whether or not Mainframe Access Source Connect and Drag & Drop services are to be activated. Specify YES to activate these services or NO to disable these services. The default value is YES (the recommended setting). |
| MFADIRECT_MAXTASKS2 | The number of z/OS subtasks (TCBs) to be started and dedicated to processing requests from Mainframe Access Drag & Drop and Source Connect clients, including Mainframe Access client functions originating in Mainframe Express and other development environment clients. Specify 0 (zero) or a positive integer value between 1 and 50. The default value is 5. |
| MFA_ENDEVOR_HISTORY | YES is the default. This will dynamically create a cumulative Endevor transaction history file (MFALOGE) to house the access history of all file access attempts using Endevor. The Endevor API interface produces this log for each access requested. |
| MFA_ENDEVOR_INTERFACE | YES is the default. Specify NO to prevent MFA Server from offering access to Endevor services. |
| MFA FEATURE | Indicates whether or not communication with the Mainframe Access Data Connect server is to be activated. Specify YES to activate the Mainframe Access Data Connect feature or NO to deactivate it. |
| MFA_LIBRARIAN_HISTORY | YES is the default. This will include a summary audit trail of all LIBRARIAN data accesses as part of the MFALOG output log. |
| MFA_LIBRARIAN_DIR_INFO | LONG is the default. This directs MFA Server to request complete member information from Librarian. The LONG specification significantly increases response time when accessing Librarian master files containing over 1,000 members. Specify SHORT to reduce the amount of member information requested from Librarian. |
| MFA_LIBRARIAN_INTERFACE | YES is the default. Specify NO to prevent MFA Server from offering access to Librarian services. |
| MFA_LIBRARIAN_UPD_MODULE | The name of the Librarian Batch update utility originally shipped as AFOLIBR by Computer Associates. If this module has not been renamed, then this parameter need not be specified. |
| MFALINK_MAXTASKS2 | The number of z/OS subtasks (TCBs) to be started and dedicated to processing requests from Mainframe Access Data Connect clients including Mainframe Access client functions originating in COBOL development environment clients. Specify 0 (zero) or a positive integer value between 1 and 50. |
| MFA_MCG_DB2CONNECTION | Controls which attachment facility is used by Mainframe Access Server for DB2 connections. Specify CAF (to use the DB2 call attach facility) or RRSAF (to use the DB2 Recoverable Resource Manager Services attachment facility). RRSAF is the default if this parameter is omitted. |
| MFA_PANVALET_HISTORY | YES is the default. This will include a summary audit trail of all user accesses to Panvalet as part of the MFALOG output log. |
| MFA_PANVALET_INTERFACE | YES is the default. Specify NO to prevent MFA Server from offering access to Panvalet services. |
| MFA_PANVALET_UPD_MODULE | The name of the Panvalet Batch update utility originally shipped as PAN#1 by Computer Associates. If this module has not been renamed, then this parameter need not be specified. |
| MFA_SAF_HISTORY | YES is the default. This will include a summary audit trail of all file access authorizations as part of the MFALOG output log. |
| MFA_SYSOUT_CLASS | Default value is A. This is used as the SYSOUT class for any held data produced by Mainframe Access. This includes MFALOG, MFALOGE, and SNAPDUMP message files. |
| MFA_SYSOUT_DEST | Default value is LOCAL. This is used as the SYSOUT destination for any held data produced by Mainframe Access. This includes MFALOG, MFALOGE, and SNAPDUMP message files. |
| NETWORK ID | The SSCP network ID used by ACF/VTAM on this z/OS system. This parameter must match the NETID parameter in the active ATCSTRxx VTAM start parameters member of VTAMLST. This Network ID value is used by Mainframe Access to build an LUWID (SNA Logical Unit of Work ID for LU6.2) when an LU6.2 conversation is allocated to the DB2 DDF. Specify the 1 to 8 character Network ID from ACF/VTAM's startup parameters. |
| ORGANIZATION | Your company name or other meaningful identifier up to 40 characters in length. Spaces are not permitted. Use underscores or other non-blank characters to separate words if necessary. |
| PEM FEATURE | Indicates whether or not the Mainframe Access Password Expiration Manager (PEM) feature is to be activated. The PEM feature must be active to allow Web Administration to access the operating system SAF interface for authentication of administration users. If PEM is not active, Web Administration will only verify that the logon userid is properly defined in the Mainframe Access access list dataset and no SAF authentication of the password data will be requested. PEM is also used in some Micro Focus client products to allow users of the client software on PCs to change passwords for their z/OS user IDs without logging on directly to z/OS. This is especially useful when the security subsystem indicates that the current password is expired and must be replaced. Specify YES (this setting is recommended) to activate the PEM feature or NO to deactivate it. |
| REMOTE IMS FEATURE | Indicates whether or not communication with IMS subsystems used by the IMS Option (Remote IMS) is to be activated. Specify YES to activate the Remote IMS feature or NO to deactivate it. |
| ROUTE | The message route codes to be used by Mainframe Access when console messages are issued using the z/OS WTO (Write to Operator) and WTOR (Write to Operator with Reply) services. See your IBM system documentation for valid values. |
| SMF_RECORDID | The SMF user record ID that Mainframe Access should use when writing SMF (IBM's System Management Facility) records to the z/OS SMF data sets. If an SMF user record ID is specified, that ID value should be assigned to Mainframe Access exclusively. Specify a valid SMF user record ID number to activate the Mainframe Access SMF support. Specify 0 (zero), or omit the parameter altogether, to disable the writing of SMF records. |
| SYSOUT | The SYSOUT class for the XDBOUT data set if it is dynamically allocated. Mainframe Access operational messages and trace data (when TRACE=SYSPRINT is specified and tracing is active) are written to this data set. XDBOUT is dynamically allocated to this SYSOUT class if an XDBOUT DD statement is not present in the Mainframe Access JCL. Specify a SYSOUT class designator that is valid for your z/OS system. |
| TCP LINK FEATURE 4 | Indicates whether or not the TCP/IP connection feature is to be activated. You must specify YES. |
| TCPACCESS | Selects the TCP/IP stack to be used. Specify NO (the default) to use the IBM TCP/IP stack. Specify YES if you are using the CA TCPaccess stack. |
| TCP_PORT 5 | The port number to accept connections from Micro Focus clients other than HTTP clients (see ADMIN_PORT). The specified port number must be reserved for Mainframe Access. You can explicitly reserve the port for Mainframe Access by updating the MVS TCP/IP profile data set. If the specified port is not available during Mainframe Access startup, startup will fail. Specify any valid TCP/IP port number. |
| TCPLINK_MAXTASKS 2 6 | The number of z/OS subtasks (TCBs) to be started and dedicated to processing requests from SQL Option for DB2 clients. Specify a positive integer value between 1 and 50. |
| TIME OUT FOR CONNECTION | The number of minutes that a client connection can remain idle, after which the connection will be broken and Mainframe Access resources dedicated to the client will be released. Resources that are released when an idle client is disconnected include allocated storage, TCP/IP resources and connections to server subsystems such as DB2, IMS, CICS and Mainframe Access. Specify 0 (zero) to disable the client timeout feature and allow unlimited idle time, or a positive integer value. |
| TIME OUT FOR INITIAL RECV | The number of seconds that the listener process (Micro Focus client listener or Web Server listener) will wait to receive the initial client message after a socket connection has been accepted from a new client. If the time value expires before a complete initial message is received, the client is disconnected and the listening process prepares to accept another client connection request. The default value of 3 seconds is appropriate for all installations. This low value helps keep the listeners running smoothly, even during occasional network and/or client malfunctions. Specify a positive integer value between 1 and 59 (inclusive) to alter the time out value. This may be useful for diagnostic purposes. |
| TRACE | The destination for trace data when tracing is
activated.
|
| TRACING | Specifies whether or not detailed tracing of Mainframe Access Server program activity should be started during initialization processing. Normally tracing should be turned off during initialization and during normal product operation. Activity tracing writes detailed information to the XDBOUT sysout data set and this can slow down performance in a busy server. Tracing is normally controlled by the TRACE ON and TRACE OFF commands after initialization is complete. The TRACING parameter makes it possible to trace the initialization activity, before the server is ready to accept TRACE ON/OFF commands. Activity trace started by the TRACING parameter can be stopped later using the TRACE OFF command. Specify YES to activate tracing during initialization or specify NO to inhibit activity tracing until a TRACE ON command is issued. |
| WEBROOT 7 | The character string that prefixes all of the Web resource data sets installed with Mainframe Access. Specify <hlq>.WEBROOT, substituting the value that was chosen for <hlq> when the software was installed. |
| WWWS_MAXTASKS 2 | The number of z/OS subtasks (TCBs) to be started and dedicated to processing HTTP requests from Web browsers. Requests for static resource such as Web pages, images, etc. are handled by these tasks. Specify a positive integer value between 1 and 50. |
Footnotes:
Mainframe Access uses the ADMUSER settings in the access list regardless of the setting of this parameter. The ADMUSER settings identify the user IDs that are authorized to access the Web Administration facilities of Mainframe Access.
Each dedicated subtask can support a large number of concurrent client connections. The number of subtasks specified determines the number of client requests that can be processed concurrently. The actual number of subtasks you should specify for optimum performance depends on the rate of client requests being generated by the entire community of connected end users. We recommend that you start with five to ten dedicated subtasks for any particular function and increase this number if your end users experience processing delays as the user community grows.
You may need to define this Mainframe Access LU name to your APPC/MVS and/or CICS subsystems before SNA sessions can be successfully established.
This parameter is provided for compatibility with previous releases. YES is forced internally and causes activation of basic support for client TCP/IP connections from SQL Option for DB2 clients and Telnet clients.
All the Micro Focus clients must specify this port number value and the TCP/IP host name or IP address of your z/OS system in their definitions of the connection to Mainframe Access.
If you specify a value of 0 (zero) for the TCPLINK_MAXTASKS parameter, Mainframe Access overrides this value to provide a small number of these subtasks for internal functions. This is true even if you are not using SQL Option for DB2.
The installation process creates the following final product data sets for Web resources:
The SERVERS definitions describe both application servers and target servers. Target server definitions provide an ID label and the LU 6.2 parameters needed to contact the server using SNA LU 6.2 protocols. The ID label is used in some client configurations to select a specific target server.
Application servers define address spaces that can be started and controlled by Mainframe Access server. The definition provides a JCL procedure name that can be used to start the address space, a server program name, values that govern the number of address spaces that can be started, etc.
If you will be using CICS Option or IMS Option, you must edit the Mainframe Access sample target server definitions located in member SERVERS to customize them for your system. The application server and target server definitions for the Mainframe Access Data Connect server will need to be edited only if you have changed the JCL procedure name or the VTAM APPL ACBNAME, or if the default logmode name cannot be used. All parameters for one target server should be grouped together following the <…ID…> assignment that starts the definition. The <END> statement is used to end each target server definition. All parameters for one application server should be grouped together following the <ASGROUP…> assignment that starts the definition. The <END> statement is used to end each application server definition.
The sample definitions for target servers that you will not be using can be left as they are and they will not affect the operation of Mainframe Access with target servers that you have customized. For example, if you are not using CICS Option you can leave the sample CICS target server definitions unchanged in the SERVERS member; or you can change each line of the unused definitions to a comment by inserting an asterisk in column 1; or you can delete them altogether.
The sample server definitions are provided here as a convenient reference while you read. Lines that begin with an asterisk are treated as comments and are skipped in processing.
*--------------------------------------------------------------------* * * * Micro Focus Mainframe Access - Server Definitions * * * * For minimum customization during installation you should review * * the following parameters and change them to suit your * * installation, if necessary. These customizations will allow you * * to complete the installation and perform basic installation * * verification testing. These minimum customizations are also * * sufficient to enable testing of MFA and MFE SQL Option client * * functions. * * * * ASPROC=MFAS update if you changed the name of the MFAS sample * * JCL procedure for the MFA Data Connect server * * * * ASPROC=MFAAS update if you changed the name of the MFAAS * * sample JCL procedure for the Application Servers. * * * * LUNAME=MFA62ACB update if you changed sample MFAVTAM. * * This name must match the name in the MFAVTAM * * definition and the startup parameter value on * * the MFAS PROC statement. * * * * Additional customization and/or setup work is required to enable * * the use of other product functions. After installation * * verification testing, refer to the product documentation to * * continue with customization for these additional functions: * * * * MFE CICS Option * * MFE IMS Option * * SOA Express IMS support * * ES/MTO * * * * Change Log * * * * * * ChangeID Description * * -------- -------------------------------------------------------- * * WS06 New server definition - Two ES/MTO server samples added * *--------------------------------------------------------------------* * *--------------------------------------------------------------------* * Application Server address space definitions * *--------------------------------------------------------------------* * * Mainframe Access Server (Data Connect) address space * <ASGROUP=MFAS> ASPROC=MFAS ASJOB=* ASSERVER=MFARSC00 ASMINIMUM=1 ASMAXIMUM=1 ASGROUPID=0 <END> * * Mainframe Access Application Server(s) for Endevor * <ASGROUP=ENDV> ASPROC=MFAAS ASJOB=MFAE ASSERVER=DACALL ASMINIMUM=0 ASMAXIMUM=2 ASGROUPID=0 <END> * * Mainframe Access Application Server(s) for CG processing * <ASGROUP=CGMQ> ASPROC=MFAAS ASJOB=MFAC ASSERVER=DACALL ASMINIMUM=0 ASMAXIMUM=2 ASGROUPID=0 <END> * *-------------------------------------------------------------------- * MFA Data Connect server - only one DEFAULT server is supported *-------------------------------------------------------------------- * <MFAID=DEFAULT> LUNAME=MFA62ACB TPNAME=FILESHR2 MODENAME=#INTER SYNCLEVEL=1 SECURITY=NONE <END> * *-------------------------------------------------------------------- * Sample IMS servers - multiple servers may be defined *-------------------------------------------------------------------- * <IMSID=IMSA> LUNAME=IMSSYSA TPNAME=MFDBTP6 MODENAME=IBMRDB SYNCLEVEL=0 SECURITY=NONE <END> * <IMSID=DEFAULT> LUNAME=IMSTEST TPNAME=MFDBTP6 MODENAME=IBMRDB SYNCLEVEL=0 SECURITY=NONE <END> * *-------------------------------------------------------------------- * Sample CICS servers - multiple servers may be defined *-------------------------------------------------------------------- * <MCOID=CICA> LUNAME=CICSSYSA TPNAME=* MODENAME=#INTER SYNCLEVEL=0 SECURITY=NONE <END> * <MCOID=DEFAULT> LUNAME=CICSTEST TPNAME=* MODENAME=#INTER SYNCLEVEL=0 SECURITY=NONE <END> * *-------------------------------------------------------------------- * Sample ES/MTO servers - multiple servers may be defined *-------------------------------------------------------------------- * <ES/MTOID=MTO1> ACBNAME=MFAMTO1 IPADDRESS=YOUR.MTO.HOSTNAME PORT=2200 SESSIONS=4 SOCKETS=1 <END> * <ES/MTOID=MTO2> ACBNAME=MFAMTO2 IPADDRESS=101.102.103.104 PORT=3300 SESSIONS=4 SOCKETS=1 <END> * *-------------------------------------------------------------------- * Sample CG MQ OTMA queue defintions - multiple queues may be defined *-------------------------------------------------------------------- * <CGMQOTMA=MYQ1> QMANAGER=QMG1 QUEUE=MESSAGE.QUEUE.NUMBER1 ASGROUP=CGMQ WAIT=4 <END> * <CGMQOTMA=MYQ2> QMANAGER=QMG2 QUEUE=MESSAGE.QUEUE.NUMBER2 ASGROUP=CGMQ WAIT=4 <END> *
| Parameter | Description |
|---|---|
| <ASGROUP=MFAS> | Signals the beginning of a Mainframe Access Data Connect application server definition. The group name must be MFAS for the Data Connect server. Specify MFAS. |
| ASPROC | The name of the started task JCL procedure that can be used to start the Data Connect server. This procedure must be stored in a procedure library that is available to z/OS START command processing. The Mainframe Access Data Connect server JCL is distributed as member MFAS but this name may be changed to suit your installation. Specify a JCL procedure name of up to eight characters. |
| ASJOB | The jobname prefix to be used for address spaces that are started for this group. For multiple-instance address spaces this is a prefix of 1 to 4 characters and Mainframe Access server will pad this prefix to a full 8-character jobname by appending a 4 to 7 digit sequence number. For example, ASJOB=ABC will result in jobnames ABC00001, ABC00002, etc. If you specify an asterisk (*) for this parameter the JCL procedure name is used for the jobname. This is appropriate for single-instance application server address spaces. The Mainframe Access Data Connect server is single-instance (only one will be started) and the JCL procedure name is appropriate for the jobname, also. Specify *. |
| ASSERVER | Specifies the name of the processing module for requests sent to this application server. Specify MFARSC00. |
| ASMINIMUM | Specifies the minimum number of address spaces that Mainframe Access server will start for a multiple-instance group during initialization. Mainframe Access Data Connect server is a single-instance server. Specify 1. |
| ASMAXIMUM | Specifies the maximum number of address spaces that Mainframe Access server will start for a multiple-instance group. Additional address spaces beyond the minimum will be started in response to transaction load, up to the maximum allowed by this specification. Mainframe Access Data Connect server is a single-instance server. Specify 1. |
| ASGROUPID | Specifies a numeric ID that can be used in client requests to identify this application server group. Data Connect clients do not use the ASGROUPID feature. Specify 0. |
| <END> | Signals the end of this application server definition. |
These statements define an ES/MTO server and provide MFA Server with the information needed to establish a TCP/IP socket connection to the ES/MTO server. This definition also creates a VTAM ACB that represents the ES/MTO server to the z/OS CICS system(s).
| Parameter | Description |
|---|---|
| <ES/MTOID=xxxx> | Signals the beginning of an ES/MTO target server definition and assigns an ID to this server definition. The MTOID can be one to four characters in length and must match the SYSID of the ES/MTO server being defined. The initial connection messages exchanged by MFA Server and ES/MTO use this MTOID. |
| ACBNAME | The name of the VTAM ACB associated with this ES/MTO server. MFA Server OPENs and initializes this ACBNAME during startup. The z/OS CICS system(s) must be configured to communicate with this ES/MTO server through this VTAM ACB name using CICS CONNECTION and SESSIONS definition statements. |
| IPADDRESS | The internet host name or IP address of the ES/MTO server. Specify either the host name that resolves to the correct IP address or the actual IP address in standard dotted-decimal format. The combination of IPADDRESS and PORT from this definition provides MFA Server with the information it needs to originate a socket connection to ES/MTO and to verify the authenticity of a socket connection request from ES/MTO. |
| PORT | The port number where ES/MTO is listening for ISC connections. |
| SESSIONS | Specifies the number of concurrent conversations MFA Server can initiate to the ES/MTO server over a single socket connection. If ES/MTO has a different definition for the number of concurrent sessions, the session count is negotiated to a common value at the time a socket connection is established. Specify a value that supports the required number of concurrently active conversations for your application. |
| SOCKETS | Specifies the maximum number of concurrent socket connections between MFA Server and the ES/MTO server. ES/MTO support is currently limited to a single socket connection between MFA Server and an ES/MTO server; therefore, specify a value of 1. |
| <END> | Signals the end of this target server definition. |
| Parameter | Description |
|---|---|
| <MFAID=DEFAULT> | Signals the beginning of a Mainframe Access Data Connect target server definition. Data Connect client requests do not specify a target server ID and Mainframe Access always looks for the DEFAULT Mainframe Access Data Connect target server definition. Specify DEFAULT. |
| NETID | The network ID of your SNA network. Specify a network ID of up to eight characters. |
| LUNAME | The LU name of the Mainframe Access Data Connect server (also known as the ACBNAME or VTAM APPLID). Specify an LU name of up to eight characters. |
| TPNAME | The transaction program name for Mainframe Access Data Connect server requests. Specify FILESHR2. |
| MODENAME | The SNA log mode name that will be used by Mainframe Access to indirectly specify SNA session parameters when Mainframe Access initiates sessions with the Mainframe Access Data Connect server. Specify a log mode name for LU6.2 sessions of up to eight characters. This log mode name must be present in the VTAM log mode table available to Mainframe Access. IBM's default log mode table, ISTINCLM, typically provides several standard log modes that can be used by Mainframe Access, including both IBMRDB and #INTER LU6.2 log modes. |
| SYNCLEVEL | The SNA LU6.2 sync level option to be used on conversations with the Mainframe Access Data Connect server. Specify 1. Conversations use LU6.2 CONFIRM protocols. |
| SECURITY | The security level to be indicated in SNA LU6.2 Attach FMH-5 requests sent to the Mainframe Access Data Connect server. Mainframe Access forwards security subfield information as provided by the Data Connect client and sets the FMH-5 fields accordingly. Specify NONE. |
| <END> | Signals the end of this target server definition. |
| Parameter | Description |
|---|---|
| <IMSID=xxxx> | Signals the beginning of an IMS target server definition and assigns an ID to this server definition. If an IMS Option client request does not specify a target server ID or the specified target server ID does not exist, Mainframe Access selects the DEFAULT IMS target server, if one has been defined. This IMS target server ID name is used in the configuration of the Mainframe Express client. When a Remote IMS request is sent from Mainframe Express to Mainframe Access this name is sent in the request data and is used to locate the target server definition for the IMS system that will receive the request. Specify DEFAULT or an ID of up to four alphanumeric characters. |
| LUNAME | The LU name of the IMS server (also known as the ACBNAME or VTAM APPLID). Specify an LU name of up to eight characters. This name must match the ACBNAME defined in an APPC/MVS LU definition for the target IMS system. |
| TPNAME | The IMS server transaction program name for IMS Option transactions. This is the LU6.2 transaction program name that will be sent to the IMS server in SNA Attach FMH-5 requests to begin an IMS Option transaction. Specify the APPC/MVS transaction program name that was specified in the APPC/MVS definitions during installation of Remote IMS. |
| MODENAME | The SNA log mode name that will be used by Mainframe Access to indirectly specify SNA session parameters when Mainframe Access initiates sessions with the IMS server. Specify a log mode name for LU6.2 sessions of up to eight characters. This log mode name must be present in the VTAM log mode table available to Mainframe Access. IBM's default log mode table, ISTINCLM, typically provides several standard log modes that can be used by Mainframe Access, including both IBMRDB and #INTER LU6.2 log modes. |
| SYNCLEVEL | The SNA LU6.2 sync level option to be used on conversations with the IMS server. Specify 0. |
| SECURITY | The security level to be indicated in SNA LU6.2 Attach FMH-5 requests sent to the IMS server. Mainframe Access forwards security subfield information as provided by the IMS Option client and sets the FMH-5 fields accordingly. Specify NONE. |
| <END> | Signals the end of this target server definition. |
| Parameter | Description |
|---|---|
| <MCOID=xxxx> | Signals the beginning of a CICS target server definition and assigns an ID to this server definition. If a CICS Option client request does not specify a target server ID or the specified target server ID does not exist, Mainframe Access selects the DEFAULT CICS target server, if one has been defined. This CICS target server ID name is used in the configuration of the Mainframe Express client; see the chapter Configuring CICS for Communication in your Mainframe Express CICS Option Technical Guide. When a CICS Option request is sent from Mainframe Express to Mainframe Access this name is sent in the request data and is used to locate the target server definition for the CICS system that will receive the request. Specify DEFAULT or an ID of up to four alphanumeric characters. |
| LUNAME | The LU name of the CICS server (also known as the ACBNAME or VTAM APPLID). Specify an LU name of up to eight characters. |
| TPNAME | The server transaction program name for CICS Option requests. This is the LU6.2 transaction program name that will be sent to CICS in SNA Attach FMH-5 requests to begin a CICS Option transaction. Specify a transaction program name of up to eight characters or specify * to cause Mainframe Access to use the transaction program name provided by the CICS Option client. The CICS Option client prepares a partial FMH-5 request that specifies the standard CICS transaction program names for function shipping, distributed program linking and so on. |
| MODENAME | The SNA log mode name that will be used by Mainframe Access to indirectly specify SNA session parameters when Mainframe Access initiates sessions with mainframe CICS. Specify a log mode name for LU6.2 sessions of up to eight characters. This log mode name must be present in the VTAM log mode table available to Mainframe Access. IBM's default log mode table, ISTINCLM, typically provides several standard log modes that can be used by Mainframe Access, including both IBMRDB and #INTER LU6.2 log modes. |
| SYNCLEVEL | The SNA LU6.2 sync level option to be used on conversations with CICS. Specify 0. |
| SECURITY | The security level to be indicated in SNA LU6.2 Attach FMH-5 requests sent to the CICS server. Mainframe Access forwards security subfield information as provided by the CICS Option client and sets the FMH-5 fields accordingly. Specify NONE. |
| <END> | Signals the end of this target server definition. |
The SOA Express IMS eBiz transactions (message processing programs) are loaded and executed in application server address spaces. One or more groups of application server address spaces can be defined for SOA Express IMS support. The parameters in each group definition provide information that Mainframe Access Server needs in order to start and manage the associated address spaces.
| Parameter | Description |
|---|---|
| <ASGROUP=CGMQ> | Signals the beginning of an address space group definition. The assigned group name (CGMQ in the sample definition) is referenced by Mainframe Access Server queue definitions (in the SERVERS member) that will use the address spaces defined by this group. Although a single group will satisfy the needs of most installations, multiple address space groups may be defined for SOA Express processing. This might be done to separate distinct workloads for usage reporting, workload management, etc. Unique group names should be specified for each group and the queue definitions must refer back to the appropriate definition using the group name. Specify a group name of up to four characters. |
| ASPROC | The name of the started task JCL procedure that can be used to start address spaces for this group. Sample JCL procedure MFAAS provides the basic JCL for an application server address space. Sample MFAAS contains comments that describe how to add your SOA Express eBiz program library definition(s) to the JCL procedure. Specify a JCL procedure name of up to eight characters. |
| ASJOB | The jobname prefix to be used for address spaces that are started for this group. For multiple-instance address spaces this is a prefix of 1 to 4 characters and Mainframe Access Server will pad this prefix to a full 8-character jobname by appending a 4 to 7 digit sequence number. For example, ASJOB=MFAC will result in jobnames MFAC0001, MFAC0002, etc. SOA Express IMS support uses multiple-instance address spaces to allow concurrent execution of client requests. The sample prefix MFAC can be changed to meet the needs of your installation. If you do change the suggested prefix you will need to review the security subsystem definition for the Mainframe Access started tasks. The configuration process uses a generic STARTED task definition (the generic name specified during Quick Configuration is MFA*.*) that covers generated jobnames such as MFACxxxx, in addition to the MFA (the MFA Server control region) and MFAS (the MFA Server for Data Connect) started task names. Specify a jobname prefix of up to four characters. |
| ASSERVER | Specifies the name of the processing module for requests sent to the application server. Specify DACALL. |
| ASMINIMUM | Specifies the minimum number of address spaces that Mainframe Access server will start for a multiple-instance group during initialization. Specifying zero delays address space activation until the first client request is received. Specify a minimum value from zero up to the ASMAXIMUM value. |
| ASMAXIMUM | Specifies the maximum number of address spaces that Mainframe Access server will start for a multiple-instance group. Additional address spaces beyond the minimum will be started in response to transaction load, up to the maximum allowed by this specification. SOA Express IMS support can effectively utilize multiple address spaces to meet the concurrency requirement demanded by your transaction arrival rate. The sample suggests an initial value of 2 and this can be increased as your transaction load increases. Mainframe Access server issues messages (to the XDBOUT data set) when a client request must be queued to wait for an available processing address space. Increase the ASMAXIMUM value (by 1) when you observe frequent queueing of client requests. Specify a value from 1 to 10. |
| ASGROUPID | Specifies a numeric ID that can be used in client requests to identify this application server group. SOA Express clients do not use the ASGROUPID feature. Specify 0. |
| <END> | Signals the end of this application server definition. |
Each MQ Series message queue to be monitored by Mainframe Access Server's SOA Express IMS support must be defined in the SERVERS member. When support for this feature is activated via the CGMQOTMA FEATURE=YES specification in the PARMS member, Mainframe Access Server initialization processes the queue definitions and creates a listener task in the control region for each queue. The listener for a queue starts a message processing program for each message that arrives on the queue. The message processing programs run in the Mainframe Access application server address space(s) of the address space group associated with the queue. The message processing program in the dependent region dequeues the message and runs the associated eBiz program to drive the target IMS system using the IBM IMS OTMA feature. The message processing program returns the results to the requesting client in a MQ message.
| Parameter | Description |
|---|---|
| <CGMQOTMA=name> | Signals the beginning of a SOA Express message queue definition and assigns a Mainframe Access Server name to the definition. The assigned name is used in messages about this message queue definition. A unique names should be specified for each queue definition. Specify a name of up to four characters. |
| QMANAGER | Names the MQ Series queue manager that manages the message queue being defined. Specify the 1 to 48 character name of the MQ Series queue manager. |
| QUEUE | Names the queue that is to be monitored for SOA Express client messages. The QMANAGER/QUEUE name pairs should be unique in the Mainframe Access Server definitions. Specify the 1 to 48 character name of the MQ Series message queue. |
| ASGROUP | Specifies the name of the ASGROUP that defines a set of application server address spaces that can be used to run the message processing program for messages that arrive on this queue. This name associates the queue definition with an application server definition. The application server definition defines how the processing address spaces are started (that is, the JCL to be used, the started task name for the address space, etc.). The sample SERVERS member includes a definition for the CGMQ address space group. Specify the one to four character ASGROUP name to be associated with this queue. |
| WAIT | Specifies the number of seconds that the listener task should allow MQ Series to hold a receive request pending when no messages are immediately available. Allowing MQ Series to hold the receive request pending reduces unproductive processing in the Mainframe Access Server listener task. The default value for this parameter is 5 seconds. Specify a wait time value of 1 to 15 seconds. |
| <END> | Signals the end of this application server definition. |
| Parameter | Description |
|---|---|
| <ASGROUP=ENDV> | Signals the beginning of the application server definition for Mainframe Access Endevor support. The group name must be ENDV. Specify ENDV. |
| ASPROC | The name of the started task JCL procedure that can be used to start address spaces for this group. Sample JCL procedure MFAAS provides the basic JCL for an application server address space. Refer to the section Endevor in the appendix External Library Management Systems to learn how to customize this JCL for Endevor support. Specify a JCL procedure name of up to eight characters. |
| ASJOB | The jobname prefix to be used for address spaces that are started for this group. For multiple-instance address spaces this is a prefix of 1 to 4 characters and Mainframe Access Server will pad this prefix to a full 8-character jobname by appending a 4 to 7 digit sequence number. For example, ASJOB=MFAE will result in jobnames MFAE0001, MFAE0002, etc. Endevor support multiple-instance address spaces to allow concurrent execution of client requests. The sample prefix MFAE can be changed to meet the needs of your installation. If you do change the suggested prefix you will need to review the security subsystem definition for the Mainframe Access started tasks. The configuration process uses a generic STARTED task definition (the generic name specified during Quick Configuration is MFA*.*) that covers generated jobnames such as MFAExxxx, in addition to the MFA (the MFA Server control region) and MFAS (the MFA Server for Data Connect) started task names. Specify a jobname prefix of up to four characters. |
| ASSERVER | Specifies the name of the processing module for requests sent to the application server. Specify DACALL. |
| ASMINIMUM | Specifies the minimum number of address spaces that Mainframe Access server will start for a multiple-instance group during initialization. Specifying zero delays address space activation until the first client request is received. Specify a minimum value from zero up to the ASMAXIMUM value. |
| ASMAXIMUM | Specifies the maximum number of address spaces that Mainframe Access server will start for a multiple-instance group. Additional address spaces beyond the minimum will be started in response to transaction load, up to the maximum allowed by this specification. Endevor support can effectively utilize multiple address spaces to meet the concurrency requirement demanded by your transaction arrival rate. The sample suggests an initial value of 2 and this can be increased as your transaction load increases. Mainframe Access server issues messages (to the XDBOUT data set) when a client request must be queued to wait for an available processing address space. Increase the ASMAXIMUM value (by 1) when you observe frequent queueing of client requests. Specify a value from 1 to 10. |
| ASGROUP | Specifies a numeric ID that can be used in client requests to identify this application server group. The Mainframe Access Endevor clients do not use the ASGROUP ID feature. Specify 0. |
| <END> | Signals the end of this application server definition. |
ChangeMan requests are processed in application server address spaces. A single group of application server address spaces can be defined for ChangeMan processing. The parameters in the group definition provide information that Mainframe Access Server needs in order to start and manage the associated address spaces.
ChangeMan processing is associated with a specific address space group by the Mainframe Access Server startup parameter CHANGEMAN_ASGROUP in the PARMS member. The sample ASGROUP named CGMQ (see the section Application Server Parameters for SOA Express IMS Support) is shared by SOA Express and ChangeMan processing. You may want to create a distinct ASGROUP definition for ChangeMan processing. This might be done to separate the workload for usage reporting, workload management, etc.
The MFAAS JCL sample referenced in the address space group definition contains comments that describe how to customize this JCL for ChangeMan processing.
You must edit the access list definitions located in member ACCESS to customize them for your installation. There are two types of definition in this list:
The sample access list definitions are provided here as a convenient reference while you read. Lines that begin with an asterisk are treated as comments and are skipped in processing.
*--------------------------------------------------------------------* * * * Micro Focus Mainframe Access - Access List * * * *--------------------------------------------------------------------* * *--------------------------------------------------------------------* * Permission list * *--------------------------------------------------------------------* * PERMIT=111.111.111 * *--------------------------------------------------------------------* * Rejection list * *--------------------------------------------------------------------* * REJECT=222.222.222 * *--------------------------------------------------------------------* * Web Administration users * *--------------------------------------------------------------------* * ADMUSER=MFAUSER * END
If you specify ACCESS LIST CHECK=YES in the Mainframe Access parameter file and specify the access list filename in an //XDBACC DD statement in the Mainframe Access startup JCL, client connection requests are accepted or rejected according to the values you specify for the PERMIT and REJECT parameters:
PERMIT=ipaddress REJECT=ipaddress
The format of the IP address is the familiar dotted decimal notation. A complete Internet address consists of four decimal numbers or address groups, each in the range 0 through 255, with the groups being separated by decimal points.
You can specify complete Internet addresses to permit or reject individual clients.
You can also specify a range of consecutive Internet addresses in a single statement, by omitting one or more trailing address groups. This is known as a masked address specification. To decide whether or not a particular request is to be allowed, Mainframe Access first shortens the client address by removing trailing address groups that correspond to address groups omitted in the specification, then compares the shortened address with the masked address.
If you are using the access list mechanism, client connection requests from all addresses not specified in PERMIT or REJECT parameters are rejected.
Here are two example sets of access list parameters
PERMIT = 111.111.148 REJECT = 111.111.148.244
The effect of these parameter values is that all client connection requests from IP addresses in the range 111.111.148.0 to 111.111.148.255 are accepted with the exception of client address 111.111.148.244. Client connections from all other IP addresses are rejected.
PERMIT = 11.1.82 REJECT = 11.1.82.4 PERMIT = 111.202.111.18
The effect of these parameter values is that all client connection requests from IP addresses in the range 11.1.82.0 through 11.1.82.255 are accepted with the exception of client address 11.1.82.4. Client connections requests from the address 11.202.111.18 are also accepted. Connection requests from all other IP addresses are rejected
Access to the Web Administration feature is available only to users specified as administration users in the access list. You specify each administration user with a separate ADMUSER entry in the access list:
ADMUSER=userid
You can specify any user ID that is already defined to your security subsystem (or will be subsequently defined). This includes user IDs that are already defined for access to TSO, IMS, CICS or other z/OS subsystems. When an administration user enters a user ID and password on the Web Administration sign-on page, Mainframe Access calls the security subsystem to authenticate the user by verifying that the password supplied is valid for that user. If the security subsystem rejects the password the user is denied access to the Web Administration home page.
Here is an example:
ADMUSER=ANNZ ADMUSER=BRUCEY
All Web Administration sign-on requests from these users are accepted if they are accompanied by their current passwords as maintained by the security subsystem. A sign-on request from CHRISW (or any other user), even when accompanied by a valid password, is denied access to Web Administration.
The Mainframe Access audit log feature uses a VSAM data set to record client login and logout information. The information that is logged includes the user ID, client IP address, login and logout times, target server name and encryption usage. If you want to use the audit log feature you need to prepare the audit log data set and update the Mainframe Access JCL procedure.
Sample member AUDIT contains the JCL to allocate and initialize a Mainframe Access audit log VSAM data set. Edit the JOB card, data set names and volume serial number information, then submit the job and verify that the condition code for the INITLOG step is 0 (zero). Note that a condition code of 8 for the ALLOCLOG step is normal the first time that you run this job.
When editing the data set names you may use a global change command to change all instances of HLQ to the high level qualifier that you selected for Mainframe Access data sets during the installation procedure.
Edit the Mainframe Access startup JCL to make the audit log data set available. Do this by removing the keyword DUMMY and the trailing comma (DUMMY,) from the XDBAUDIT DD statement:
//*
//*-----------------------------
//* Optional audit log data set
//*-----------------------------
//*
//XDBAUDIT DD DUMMY,DISP=SHR,DSN=&DSNQUAL..AUDIT
If you are using IBM's TCP/IP, you can add the Mainframe Access started task name (the name of the Mainframe Access JCL procedure in the system procedure library) to the TCP/IP autolog list. TCP/IP will then automatically start Mainframe Access when it starts and stop Mainframe Access when it stops. Do not perform this update until you have finished configuring Mainframe Access and are satisfied with the way Mainframe Access is running.
Mainframe Access provides sample members MFAGTF and GTFCNTL to assist you when you need to use IBM's Generalized Trace Facility (GTF) to obtain trace data for problem determination. In some problem situations our Product Support will request a VTAM trace of an application LU, usually the Mainframe Access server LU.
Sample JCL to run GTF as a started task is provided in member MFAGTF. Edit this JCL to customize the data set names for your installation and then copy the JCL into a system procedure library that is available when z/OS START commands are processed. Member GTFCNTL contains GTF control statements that are referenced by the sample GTF JCL procedure. The USR=(FF1,FEF,0E9) statement in this member specifies the recording of VTAM buffer trace records (FF1 and FEF) and Mainframe Access server trace records (0E9).
Note: If you change the Mainframe Access EID=00E9 parameter setting (Editing Mainframe Access Parameters), you should update member GTFCNTL with the new value.
After you customize and install procedure MFAGTF you can test out the procedure by issuing the following z/OS START command at a system console or using the TSO/ISPF SDSF command facility:
S MFAGTF.MYGTF
GTF will start and read the GTFCNTL parameter file. When the initialization complete message is issued GTF is ready to record trace data.
S MFAGTF.MYGTF
$HASP100 MFAGTF ON STCINRDR
IEF695I START MFAGTF WITH JOBNAME MFAGTF IS ASSIGNED TO USER RWITEK, GROUP CSIDVLP
$HASP373 MFAGTF STARTED
IEF403I MFAGTF - STARTED - TIME=19.08.44
AHL121I TRACE OPTION INPUT INDICATED FROM MEMBER GTFCNTL OF PDS
<hlq>.CNTL
TRACE=USRP
USR=(FF1,FEF,0E9)
END
AHL103I TRACE OPTIONS SELECTED --USR=(FEF,FF1,0E9)
AHL906I THE OUTPUT BLOCK SIZE OF 27998 WILL BE USED FOR OUTPUT 228
DATA SETS:
<hlq>.TRACE
AHL080I GTF STORAGE USED FOR GTF DATA: 229
GTFBLOCK STORAGE 82K BYTES (BLOK= 40K)
PRIVATE STORAGE 1038K BYTES
SADMP HISTORY 54K BYTES (SADMP= 40K)
SDUMP HISTORY 54K BYTES (SDUMP= 40K)
ABEND DUMP DATA 0K BYTES (ABDUMP= 0K)
AHL031I GTF INITIALIZATION COMPLETE
You stop GTF by issuing the following z/OS STOP command at a system console or using the TSO/ISPF SDSF command facility:
P MYGTF
GTF acknowledges the stop command and closes down, as shown in the following example:
P MYGTF AHL006I GTF ACKNOWLEDGES STOP COMMAND IEF404I MFAGTF - ENDED - TIME=19.10.31 $HASP395 MFAGTF ENDED $HASP250 MFAGTF PURGED -- (JOB KEY WAS B9C101AA)
Mainframe Access server is a robust server that is designed to efficiently handle all of the different client access requirements in high-volume usage. A single instance of Mainframe Access server will most likely meet the needs of your installation. It is, however, possible to run multiple instances of Mainframe Access server on your z/OS system. This might be desirable for establishing test and production servers, isolating specific user groups in their own server, isolating specific feature activations, etc.
Once you have a successful Mainframe Access server installation you can easily create additional instances as follows:
Copyright © 2007 Micro Focus (IP) Ltd. All rights reserved.