| |
Home |
![[Table of Contents]](/dwicons/b_toc.gif)
|
Installation and Administration Guide for Mainframe Connect for DB2 MVS-CICS |
![[-]](/dwicons/i_colpse.gif)
| Chapter 4 Installing the MainframeConnect for DB2/MVS-CICS Tape |
Chapter 4
This chapter contains instructions for installing the MainframeConnect for DB2/MVS-CICS tape.
Warning!
You must install the Open ServerConnect for CICS/MVS base tape before you install MainframeConnect for DB2/MVS-CICS. See the Installation and Administration Guide for Open ServerConnect for IBM CICS/MVS for instructions.
The sections in this chapter are:
A CICS system programmer, a DB2 database administrator, and a DirectConnect administrator are required to successfully install the MainframeConnect for DB2/MVS-CICS tape. Make sure that these persons are prepared to perform their respective tasks.
Please read through all of the following steps before beginning the installation. To help identify who is responsible for which steps, margin captions indicate the type of system programmer or administrator who performs them.
Retrieve the JCL that copies the MainframeConnect for DB2/MVS-CICS libraries from the tape by entering the following JCL and submitting the job. You can use the default values or change them to be specific to your site. A reminder to verify the defaults appears on the right.
//JOBNAME JOB (ACCTNR,ACCTINFO),'UNLOAD MC' <== VERIFY //* //* Retrieve the JCL that copies the Sybase libraries from //* the installation tape, MFC120, to disk. //* //GENER EXEC PGM=IEBGENER //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY //SYSUT1 DD DSN=SYBASE.AMD2120.TAPEJCL, // DISP=(OLD,KEEP), // UNIT=3480, <== VERIFY // LABEL=(1,SL),VOL=SER=MFC120 //SYSUT2 DD DSN=SYBASE.AMD2120.CICSDB2.TAPEJCL, <== VERIFY // UNIT=SYSDA,VOL=SER=SYB001, <== VERIFY // DISP=(,CATLG,DELETE), // SPACE=(3120,(10,3))
Retrieve MainframeConnect for DB2/MVS-CICS from the tape into DASD by editing and submitting the JCL from the TAPEJCL file you unloaded in step 1. Editing instructions are in the JCL.
If the VSAM log files are not defined, define the AMD2 transaction VSAM logfiles by editing and submitting JCL member AMD2LOG.
Warning!
If you change the logfile default names in step 3, be sure you also change the default names in step 4.
If you use RDO (Resource Definition Online) to define resources at your site, edit and submit CTRL member AMD2RDO according to the instructions contained in the CTRL library. This job defines all Sybase resources to CICS through RDO using the DFHCSDUP utility.
If you do not use RDO to define resources, create the appropriate FCT, PCT, and PPT definitions based on the information in the member AMD2RDO.
Edit your CICS start-up procedure, including the MainframeConnect for DB2/MVS-CICS LOADLIB library in the DFHRPL concatenation. Coordinate with the DB2 database administrator (step 6) before recycling the CICS region (step 12).
If you plan to install the MainframeConnect for DB2/MVS-CICS Catalog Stored Procedures (CSPs) for use with TRS, use the installation steps in Chapter 5, "Installing CSP'S for Transaction Router Service"
The following steps pertain to DB2 database administration. If you change default names, be sure the new names conform to your site's conventions, particularly for plan names and authorizations.
Include AMD2HRCT macro entries from the CTRL library in your RCT table, generate the table, and stop and start DSNC to activate these changes
If you change the default plan names in this step, be sure to use the new names in step 7.
Create a collection ID by issuing the following SQL to DB2 in a utility, such as TSO batch or SPUFI:
GRANT PACKADM ON COLLECTION SYAMD2 TO userid
Bind the application plan by running job BINDPLAN in the JCL library, adding a CACHE SIZE of 0 for performance.
The asterisk and period (*.) before SYAMD2.* in the PKLIST parameter of the BINDPLAN job may not be required.
Bind the AMD2 package by running job BINDPKG in the JCL library.
Create a permanent VSAM configuration dataset by modifying and running job AMD2CFG in the JCL library.
Optional. Alter the message table using AMD2CAMX in the SOURCE library as a prototype. Then, assemble and link the message table using AMD2CAMX from the JCL library.
For details on changing the message table, see Chapter 7, "Customizing MainframeConnect for DB2/MVS-CICS Messages"
If necessary, recycle your CICS region.
After you install MainframeConnect for DB2/MVS-CICS, the DB2 data administrator should perform the post-installation tasks listed in this chapter. These tasks includes:
Authorizing users for the application plan
Authorizing users for DB2 packages
Authorizing users for system tables
Verifying your installation
All users who will use MainframeConnect for DB2/MVS-CICS to access DB2 must be authorized to execute the DB2 application plan. This is the application plan you created containing all of your DB2 packages.
You can grant the privilege to all DB2 users or to specific users. To issue the GRANT statement, you can use either of the following forms:
GRANT EXECUTE ON PLAN planname TO userid
GRANT EXECUTE ON PLAN planname TO PUBLIC
where planname is the name of the DB2 application plan.
You must grant EXECUTE authority on the packages you created. Use one of the following forms:
GRANT EXECUTE ON PACKAGE AMD2.* TO userid
GRANT EXECUTE ON PACKAGE AMD2.AMD2DB2 TO userid
GRANT EXECUTE ON PACKAGE AMD2.* TO PUBLIC
GRANT EXECUTE ON PACKAGE AMD2.AMD2DB2 TO PUBLIC
If the DirectConnect for MVS users need to access catalog information from system tables and you are using catalog stored procedures (CSPs), then you must authorize users to select from the following tables:
SYSIBM.SYSCOLAUTH
SYSIBM.SYSCOLUMNS
SYSIBM.SYSDATABASE
SYSIBM.FOREIGNKEYS
SYSIBM.SYSINDEXES
SYSIBM.SYSKEYS
SYSIBM.SYSRELS
SYSIBM.SYSSYNONYMS
SYSIBM.SYSTABAUTH
SYSIBM.SYSTABLES
Some front-end applications access these system tables directly. See the application documentation for more information.
Additionally, all users accessing DB2 must be granted the appropriate authorizations on the tables they will use.
Before you configure MainframeConnect for DB2/MVS-CICS, verify that the link between MainframeConnect for DB2/MVS-CICS and DB2 is functioning correctly by accessing MainframeConnect for DB2/MVS-CICS. To do this, sign on to CICS, clear the screen, and enter:
AMD2
You should receive a message similar to the following:
MainframeConnect for DB2/MVS-CICS/12.0.0.0084 DB2 test successful
If AMD2 cannot access DB2, a message appears showing the DB2 SQLCODE; for example:
MainframeConnect for DB2/MVS-CICS/12.0.0.0084 DB2 Error was detected the SQL code is -805
See your DB2 manuals for definitions of SQL codes.
The tables in this section describe the contents of the libraries you load from the MainframeConnect for DB2/MVS-CICS tape. Step numbers that appear in parentheses indicate steps in this chapter in which members from a particular library are used.
The COPY library contains the COBOL copybook.
Member | Description |
AMD2CCPX | COBOL copybook for the parse exit routine |
The CTRL library contains macro definitions for files, transactions, programs, and plans for AMD2 to CICS. It also contains SPUFI input statements (step 4 in "Installation steps" and step 6 in "Installation steps" ).
Member | Description |
AMD2HRCT | CICS macro definitions for the AMD2 plans (if you change the plan names, you must edit this member) |
AMD2RDO | RDO definitions for CICS Version 4.x |
CREATPKG | DB2 statement for creating a collection ID |
HOSTLIB | Script for creating the host resident request library |
SPPROC | Script for creating the sp_proc and sp_proc_columns tables for the corresponding CSPs |
The DBRM library contains member AMD2DB2, which the job BINDPLAN in the JCL library binds into a package in DB2.
Member | Description |
AMD2DB2 | DBRMS for AMD2 |
The JCL library contains JCL for performing various functions while installing the MainframeConnect for DB2/MVS-CICS tape (step 3 on "Installation steps" and steps 8, 9, and 10 in "Installation steps" ).
Member | Description |
AMD2CFG | JCL for defining the configuration file |
AMD2CAMX | JCL to assemble the AMD2 message table |
AMD2LOG | JCL to define the AMD2 log files |
AMD2PXIT | JCL to compile and link AMD2CCPX, found in the SOURCE library |
BINDPKG | JCL for binding packages |
BINDPLAN | JCL for binding plans |
CSDLOAD | JCL for loading the RDO definitions |
TRSJCL | JCL for loading the TRS files from the tape |
The LOADLIB library contains pregenerated tables and programs for error messages.
Member | Description |
AMD2ACF2 | ACF2 group ID support |
AMD2CAMX | AMD2 message table |
AMD2CFG | Configuration program |
AMD2CHAB | Abend handler |
AMD2CICS | AMD2 program |
AMD2DSN | Error handler for AMD2 |
AMD2M01 | AMCF configuration map |
AMD2RACF | RACF group ID support |
AMD2SPM | Map for SPTEST |
AMD2SPT | SPTEST program for testing RSPs |
AMD2TOP | Top Secret group ID support |
The MACLIB library contains macros for working with message text and SQL codes.
Member | Description |
EXITAREA | Macro for request and result exits |
SYRTMAMT | AMD2 macro for message text |
SYRTMAMX | AMD2 macro for message attributes and SQL codes |
The SOURCE library contains a sample COBOL program and the assembler source for the AMD2 message table (see step 11 in "Installation steps" ).
Member | Description |
AMD2CAMX | Assembler source for AMD2 message table |
AMD2PXIT | Sample COBOL program using the AMD2 parse exit |
If you need to install the CSPs for use with TRS, proceed to Chapter 5, "Installing CSP'S for Transaction Router Service"
If you need to install the Japanese Conversion Module, proceed to the Installation and Administration Guide for Open ServerConnect for IBM CICS/MVS.
If you are ready to configure MainframeConnect for DB2/MVS-CICS, proceed to Chapter 6, "Configuring MainframeConnect for DB2/MVS-CICS"
|
|