Microsoft KB Archive/296120

= OLE DB provider for AS/400 and virtual storage access method host requirements =

Article ID: 296120

Article Last Modified on 4/28/2005

-

APPLIES TO


 * Microsoft SNA Server 4.0
 * Microsoft SNA Server 4.0 Service Pack 1
 * Microsoft SNA Server 4.0 Service Pack 2
 * Microsoft SNA Server 4.0 Service Pack 3
 * Microsoft SNA Server 4.0 Service Pack 4
 * Microsoft Host Integration Server 2000 Standard Edition
 * Microsoft Host Integration Server 2000 Service Pack 1

-



This article was previously published under Q296120



SUMMARY
This article describes what you have to do on the mainframe computer in order for Microsoft OLE DB Provider for the IBM AS/400 and Virtual Storage Access Method (VSAM) to access nonrelational files (VSAM files) on the mainframe.

This article also provides the requirements for the mainframe and the AS/400.



MORE INFORMATION
Microsoft OLE DB Provider for AS/400 and VSAM is implemented by using IBM open Distributed Data Management (DDM) architecture. Specifically, the provider is a DDM record-level input/output (RLIO) client that communicates with one or more IBM-implemented DDM servers. The only mainframe-based DDM server that is supported by the provider is IBM Distributed File Manager (DFM). DFM is a component of IBM Data Facility Storage Management (DFSMS) Subsystem for Multiple Virtual Storage (MVS).

Microsoft OLE DB Provider for AS/400 and VSAM requires the following on the mainframe:

DFSMS version 1 release 2 or later for MVS/ESA and OS/390

Beginning with DFM version 5 release 1, IBM only supports remote DDM client by means of Advanced Program-to-Program Communications (APPC) over SNA Logical Unit (LU) 6.2. Therefore, Microsoft OLE DB Provider for AS/400 and VSAM can only access VSAM data sets across an SNA network connection.

Support for TCP/IP is as follows:
 * TCP/IP is not supported when you are connecting the OLE DB Provider for AS/400 and VSAM to the mainframe for VSAM access.
 * TCP/IP is supported when you are connecting the OLE DB Provider for AS/400 and VSAM to the AS/400 for nonrelational data access.

For additional information about Microsoft data providers for use in a TCP/IP-only environment, click the following article number to view the article in the Microsoft Knowledge Base:

248468 Installing Microsoft SNA Server Data Providers for TCP/IP Only

Microsoft OLE DB Provider for AS/400 and VSAM requires the following on the AS/400:
 * IBM OS/400 V3R2 or later by means of APPC
 * IBM OS/400 V4R2 or later by means of APPC or TCP/IP

Configuring the Mainframe
To support Microsoft OLE DB Provider for AS/400 and VSAM for VSAM access, follow these steps:  Install the DFSMS subsystem for MVS on the mainframe.  Update Sys1.Parmlib(Appcpm ) where  is the suffix that is specified on the START APPC ('Start APPC,SUB=MSTR,APPC=xx'). Add the following to the Sys1.Parmlib member: LUADD ACBNAME(MVS1DFM)          /* ADD LU MVS1DFM TO THE            */ /*  APPC/MVS CONFIGURATION         */ SCHED(ASCH)                 /* SPECIFY THAT THE APPC/MVS        */ /*  TRANSACTION SCHEDULAR IS       */ /*  ASSOCIATED WITH THIS LU NAME   */ BASE                           /* DESIGNATE THIS LU AS THE BASE LU */ TPDATA(SYS1.APPCTP) /*  THE PERMANENT REPOSITORY FOR   */ /*  TP PROFILES FOR THIS LU        */ TPLEVEL(USER)                  /* SPECIFY THE SEARCH ORDER FOR TP  */  In the Sys1.Parmlib(Aschpm ) file, the following lines are required:  CLASSADD CLASSNAME(A)  In the Sys1.Parmlib(DFM00), the following are required:  DFM</li> LOCK_WAIT INTV(20)</li> MAX_CONV_LOCK(5)</li></ul> </li>  Add a Virtual Telecommunications Access Method (VTAM) Application Major Node for this logical unit (LU) in the Sys1.Vtamlst library: 00400  APPLDFM  VBUILD TYPE=APPL             APPLICATION MAJOR NODE 00500  *                                                                       00600   MVS1DFM APPL   ACBNAME=MVS1DFM,        ACBNAME FOR APPC FOR DFM        C 00700                  APPC=YES,                                               C 00800                  AUTOSES=1,                                              C 00900                  CMPAPPLI=4,          ALLOW THIS APPL TO SUPPORT ALL     C 01000                  CMPAPPLO=4,          LEVELS OF COMPRESSION. C 01100                 DDRAINL=NALLOW,                                         C 01200                  DLOGMOD=PA62TKNU,                                       C 01300                  DMINWNL=1024,                                           C 01400                  DMINWNR=1024,                                           C 01500                  DRESPL=NALLOW,                                          C 01600                  DSESLIM=2048,                                           C 01700                  EAS=65530,                                              C 01800                  MODETAB=ISTINCMS,                                       C 01900                  SECACPT=CONV,                                           C                       SRBEXIT=YES,                                            C                       VERIFY=NONE,                                            C                       VPACING=7 </li>  Update the APPC transaction program VSAM file (Sys1.Appctp).  You can do this through APPC Interactive System Programming Facility (ISPF) Administrator Panels. The location of these panels varies by environment, as configured by your organization. Obtain this information from the TSO/ISPF support personnel.</li> You can also do this through a batch job by using the APPC utility that is described later in this step.</li></ul>

For more information about using this utility to add a Transaction Program (TP), see the following IBM manual:

IBM z/OS V1R4.0 MVS Planning APPC Management (Document Number SA22-7599-02)

The following is sample job control language (JCL) code that you can use to add the DFM/MVS TP profile to the VSAM data set.

Note A TP profile for DFM/MVS might have been added when the DFSMS product was originally installed. //STEP    EXEC PGM=ATBSDFMU //SYSPRINT DD SYSOUT=* //SYSSDOUT DD SYSOUT=* //SYSSDLIB DD DSN=SYS1.APPCTP,DISP=SHR //SYSIN   DD DATA,DLM=XX TPADD TPNAME(¬X'07'001) ACTIVE(YES) TPSCHED_DELIMITER(##) CLASS(DEFAULT) JCL_DELIMITER(ENDJCL) //GDEDFM  JOB MSGCLASS=H,MSGLEVER=(1,1),CLASS=A //GDEDFM  EXEC PGM=GDEISASB ENDJCL XX /* </li>  In the Sys1.proclib file, make sure that the DFM start procedure ('//DFM EXEC PGM=GDEISBOT') is present. Here is a sample DFM/MVS start-up procedure: //DFM   PROC PARMS=NORMAL //************************************************************ //* ADSTAR DISTRIBUTED FILE MANAGER ADDRESS SPACE           * //************************************************************ //      EXEC PGM=GDEISBOT,PARM='&PARMS',REGION=32M,TIME=1440 //IEFPARM DD DSN=SYS1.PARMLIB,DISP=SHR //SYSPRINT DD SYSOUT=H </li> After you update the IBM mainframe system, you (the administrator) stop, and then start the APPC application. Make sure that the VTAM application (VTAM APPL) for DFM is Active before you start APPC. You can run the following commands:  v net,act,id=dfmxxxx,scope=all</li> d appc,lu,all</li></ul> </li> Finally, make sure that you run the following Start task commands: <ul> <li>start appc,sub=mstr,appc= 

(See step 2 for .)</li> <li>start asch,sub=mstr,asch= </li> <li>start dfm,sub=mstr</li></ul> </li></ol>

<div class="references_section">