This appendix provides information about upgrading to Mainframe Access
Version 3. The new Mainframe Access Version 3 server combines all of Mainframe
Manager's z/OS server functionality and Mainframe Access' z/OS file handling
functionality into a single package that retains the Mainframe Access name. The
new Mainframe Access Data Connect Version 3 server runs as an extension of
Mainframe Access Version 3 server to support the Data Connect functions of
Mainframe Access.
This section describes how to upgrade your installation from previous
versions of Mainframe Manager (Versions 2.02 and earlier) and/or Mainframe
Access (Version 2.5 and earlier) to Mainframe Access Version 3. Three upgrade
procedures are provided; one for current users of both Mainframe Manager and
Mainframe Access server, one for current users of only Mainframe Access server
and one for current users of only Mainframe Manager.
Regardless of which upgrade path you will take, the first step is to
follow the instructions on the CD to install Mainframe Access Version 3
software from the CD onto your z/OS system. We recommend that you first follow
both the upload and quick configuration instructions to create a completely new
basic installation that can run concurrently with your old versions.
When you have completed the upgrade steps you should test all of your
features and functions to verify proper operation.
Note: If you currently have Mainframe Manager clients connecting to the
Mainframe Manager TCP_PORT and Mainframe Access clients connecting directly to
a separate port defined to the Mainframe Access server you will need to change
one of the client groups to use a different port for Version 3. The TCP_PORT of
Mainframe Access Version 3 server provides the connection point for all TCP/IP
clients.
It is also possible to run two instances of Mainframe Access Version
3 server, one for existing Mainframe Manager clients and one for existing
Mainframe Access clients. In this arrangement, one server should be configured
so that TCP_PORT is the same as your existing Mainframe Manager TCP_PORT and
one server should have TCP_PORT set to the Mainframe Access server port number
that you are currently using. No client port changes would be needed using this
dual server configuration.
- If you currently use the audit log feature, update your Mainframe
Access Version 3 server startup JCL (the procedure name is MFA, as distributed
in the <hlq>.CNTL data set) by deleting "DUMMY," from the //XDBAUDIT DD
statement and changing the data set name to the name of your existing VSAM
audit log data set. Optionally, you may allocate and initialize a new audit log
data set for use with Version 3. If you edit the procedure in the CNTL data
set, be sure to copy the updated procedure into the system procedure library
that you are using.
- Replace member ACCESS in the <hlq>.CNTL data set with the
access list specifications from your current Mainframe Manager configuration.
- Edit the target server definitions in member SERVERS of the
<hlq>.CNTL data set. Replace the two sample IMS servers and the two
sample CICS servers with the IMS and/or CICS server definitions from your
current Mainframe Manager configuration. If you are not currently using
IMS and/or CICS server definitions, leave the SERVERS member unchanged.
- Edit the PARMS member in the <hlq>.CNTL data set. Compare
each parameter of the new PARMS member with your existing Mainframe Manager
parameters and, with one exception, you may change the values in the new PARMS
member to match your existing specifications. If there is a parameter in your
existing configuration that is not present in the Mainframe Access Version 3
parameters, do not copy or add this parameter to the Version 3 PARMS member. Do
not change the WEBROOT parameter to match your existing configuration. This
parameter provides the data set name prefix for dynamically allocated Web
Administration resource data sets and you will want Mainframe Access Version 3
to use the Version 3 resource data sets.
If are using CA TCPaccess as your TCP/IP stack, change parameter
TCPACCESS to specify TCPACCESS=YES.
- If you currently use FSTAB file name mapping for Data Connect, copy
your current FSTAB source statements into the Version 3 job for building the
FSTAB (the sample job is MFASFTAB, as distributed in the <hlq>.MFACNTL
data set). Your current source statements should be used to replace the source
statements in the sample job. Then run the MFASFTAB job to build your FSTAB for
Version 3.
- If you currently use the VCTL file name mapping data set for Data
Connect, copy all of your current VCTL members to the Version 3 mapping data
set, <hlq>.MFAVCTL.
- Edit the PARMS member in the <hlq>.CNTL data set. Set
TCP_PORT to the port number used by your current Mainframe Access server
installation.
If are using CA TCPaccess as your TCP/IP stack, change parameter
TCPACCESS to specify TCPACCESS=YES.
- If you currently use FSTAB file name mapping for Data Connect, copy
your current FSTAB source statements into the Version 3 job for building the
FSTAB (the sample job is MFASFTAB, as distributed in the <hlq>.MFACNTL
data set). Your current source statements should be used to replace the source
statements in the sample job. Then run the MFASFTAB job to build your FSTAB for
Version 3.
- If you currently use the VCTL file name mapping data set for Data
Connect, copy all of your current VCTL members to the Version 3 mapping data
set, <hlq>.MFAVCTL.
- If you currently use the audit log feature, update your Mainframe
Access Version 3 server startup JCL (the procedure name is MFA, as distributed
in the <hlq>.CNTL data set) by deleting "DUMMY," from the //XDBAUDIT DD
statement and changing the data set name to the name of your existing VSAM
audit log data set. Optionally, you may allocate and initialize a new audit log
data set for use with Version 3. If you edit the procedure in the CNTL data
set, be sure to copy the updated procedure into the system procedure library
that you are using.
- Replace member ACCESS in the <hlq>.CNTL data set with the
access list specifications from your current Mainframe Manager configuration.
- Edit the target server definitions in member SERVERS of the
<hlq>.CNTL data set. Replace the two sample IMS servers and the two
sample CICS servers with the IMS and/or CICS server definitions from your
current Mainframe Manager configuration. If you are not currently using IMS
and/or CICS server definitions, leave the SERVERS member unchanged.
- Edit the PARMS member in the <hlq>.CNTL data set. Compare
each parameter of the new PARMS member with your existing Mainframe Manager
parameters and, with one exception, you may change the values in the new PARMS
member to match your existing specifications. If there is a parameter in your
existing configuration that is not present in the Mainframe Access Version 3
parameters, do not copy or add this parameter to the Version 3 PARMS member. Do
not change the WEBROOT parameter to match your existing configuration. This
parameter provides the data set name prefix for dynamically allocated Web
Administration resource data sets and you will want Mainframe Access Version 3
to use the Version 3 resource data sets.
If are using CA TCPaccess as your TCP/IP stack, change parameter
TCPACCESS to specify TCPACCESS=YES.
Version 3 of Mainframe Access introduces the following changes:
- Integration of Mainframe Manager with the Mainframe Access server
Drag & Drop and Source Connect functions.
- A Dependent Address Space Services component that allows Mainframe
Access server to start and control auxiliary address spaces.
- SOA Express IMS support using MQ Series messaging to
communicate with client applications and the IBM IMS OTMA interface to drive
transactions in target IMS systems.
- Simplified installation and customization for CA TCPaccess support.
- Simplified installation and customization for Mainframe Access
server and Mainframe Access Data Connect server.
- Improved trace messaging that offers better trace performance and
time/date stamping for all trace messages.
- License key requirements are removed from Mainframe Access server
and Mainframe Access Data Connect server.
- Support has been withdrawn for Mainframe Access client connections
using SNA LU 6.2 protocols. Mainframe Access server Version 3 supports
only TCP/IP clients. Customers that require SNA LU
6.2 client connections must continue to use previous versions of Mainframe
Manager and Mainframe Access.
- Support has been withdrawn for Mainframe Access server SAF user
exits. In previous versions of Mainframe Access these user exits could be used
to customize or eliminate SAF security checks for client logons and for Drag
& Drop and Source Connect file operations. All Mainframe Access server
client logons and file operations are now SAF-validated by standard Mainframe
Access server security processing. The SAF user exits continue to be supported
by the Mainframe Access Data Connect Version 3 server for Data Connect
operations only.
Version 2 of Mainframe Manager introduces the following changes:
- A Data Set Services component, which manages input/output
operations for all types of z/OS data sets
- A new, easy-to-use interface for Web Administration
- Recovery and dumping services that help identify the cause of
software failures affecting the operation of Mainframe Manager
Version 1.17 of Mainframe Manager introduces the following changes:
- Support for Mainframe Express IMS Option over TCP/IP
- Support for Mainframe Express CICS Option over TCP/IP
- An improved port number reuse routine in TCP listeners
- Fixes for LU6.2 problems encountered in ATTN exits and SRB mode
programs
- A refresh command to refresh the server configuration parameters in
flight
Copyright © 2007 Micro Focus (IP) Ltd. All rights reserved.