Forums & Discussions Home

    A place for members, communities, and committees to have discussions online and via e-mail.
    Click a category or topic to below to start the conversation...

    You are currently in view only mode for this forum. Please click the appropriate below to login as a member and participate. If you are not a member, please CLICK HERE for more information.


    Dec 21
    1999

    accessing MVS os/390 data from PC

    [login to unmask email]
    I'm seeking some expertise in the area of PC applications accessing (reading and
    updating) data which resides on MVS OS/390.

    We have one project which unloads the MVS OS/390 data and FTP's the datasets to
    the desired platform. We have another (pilot) project which is via the WEB and
    using stored procedures - the user enters the URL , the application connects to
    DB2 and returns the WEB page/data. Is there any better possilities of
    accomplishing this task?

    I myself do not know enough about the client/server environment so that's why I
    am seeking your professional input.
    I do know however that we have concerns about locking, performance and security.
    We have seen hung threads in our DB2 subsystems (both test and production) which
    have used up so many resources that it caused our production LPAR to be IPLd.
    We have also seen instances where one client locks the DB2 catalog and causes
    numerous -911's.

    Any information is welcome and greatly appreciated.



    [login to unmask email]
    We have installed the MQSeries software to allow our PC-based applications
    (written in VB) to access our CA-IDMS database running on an MVS OS/390
    mainframe. In our case, the PC-application also accesses a DB2 UDB on an
    NT platform.

    MQSeries allows programs to talk to each other irrespective of the
    processors used, operating system, communication protocols et al. This
    involved a fair bit of work ... but very basically we'd have:

    * program on the PC would PUT a MESSAGE on the MQSeries queue (which is
    owned by a "queue manager" that is running on the PC)
    * the queue manager on the PC would pass the message to a 2nd queue
    manager running on the mainframe
    * program on the mainframe would GET the MESSAGE stored on the mainframe
    queue and process it - ie perform read or update. The result could then be
    passed back to the PC through the MQSeries gateway

    The communication between the different platforms is handled by the
    MQSeries software.

    Hope this helps.

    Milorad




    [login to unmask email]
    TATE.NE.US To: [login to unmask email]
    Sent by: DB2 cc:
    Data Base Subject: accessing MVS os/390 data from PC
    Discussion List
    <[login to unmask email]>


    22/12/1999 04:01
    Please respond
    to DB2 Data Base
    Discussion List





    I'm seeking some expertise in the area of PC applications accessing
    (reading and
    updating) data which resides on MVS OS/390.

    We have one project which unloads the MVS OS/390 data and FTP's the
    datasets to
    the desired platform. We have another (pilot) project which is via the WEB
    and
    using stored procedures - the user enters the URL , the application
    connects to
    DB2 and returns the WEB page/data. Is there any better possilities of
    accomplishing this task?

    I myself do not know enough about the client/server environment so that's
    why I
    am seeking your professional input.
    I do know however that we have concerns about locking, performance and
    security.
    We have seen hung threads in our DB2 subsystems (both test and production)
    which
    have used up so many resources that it caused our production LPAR to be
    IPLd.
    We have also seen instances where one client locks the DB2 catalog and
    causes
    numerous -911's.

    Any information is welcome and greatly appreciated.











    **********************************************************************
    This message and any attachments are confidential and for
    the addressee only. If you have received it in error, please
    notifiy the sender. It may be subject to legal privilege or
    confidentiality obligations imposed by legislation. TAC email
    addresses are for business use only. All email sent to TAC
    may be inspected and used by TAC for any lawful purpose.
    TAC policy prohibiting transmission of inappropriate material
    to its email addresses is strictly enforced.
    **********************************************************************



    Roger Miller
    [IBM Silicon Valley Lab]
    There are so many options for connecting DB2 for OS/390 with a PC.
    Most of the ones that I like best use DB2 Connect as part of the
    connection,
    but the options include MQ Series, CICS, various web connections and
    many gateway products. Don't forget stored procedures. Here are the
    primary red books with the information:

    Java Programming Guide for OS/390 , SG24-5619-00 1999-12-28

    IBM Web-to-Host Integration Update , SG24-5237-01 1999-12-23

    Developing Cross-Platform DB2 Stored Procedures: SQL Procedures and the DB2
    Stored Procedure
    Builder , SG24-5485-00 1999-12-16

    The Universal Connectivity Guide to DB2 , SG24-4894-00. 1998-02-

    Getting Started with DB2 Stored Procedures: Give Them a Call through the
    Network , SG24-4693-01
    1998-04-07

    Connecting Domino to the Enterprise Using Java , SG24-5425-00 1999-07-02


    Client/Server Implementation Using TXSeries, UDB, and VisualAge COBOL on
    Windows NT ,
    SG24-5359-00 1999-06-14

    e-business Application Solutions Using Java: Volume I , SG24-5342-00
    1999-05-24

    Accessing DB2 for OS/390 Data from the World Wide Web , SG24-5273-00
    1998-11-23


    Here are a couple of good web pages:

    http://www.ibm.com/software/ WebSphere, VisualAge,
    DB2, MQ Series, ...

    http://www.ibm.com/software/data/db2/db2connect/

    http://www.ibm.com/developer/




    All Times America/New_York

    Copyright © 2014 IDUG. All Rights Reserved

    All material, files, logos and trademarks within this site are properties of their respective organizations.

    Terms of Service - Privacy Policy - Contact