CA IDMS IUA EIUA

Fast/Access IDMSDBIO Error - 3031

  • 1.  Fast/Access IDMSDBIO Error - 3031

    Posted 02-13-2007 06:35 AM
    Hi,

    Just wondering if anyone else has experienced this problem. We are
    currently running MVS z/OS 1.4 and IDMS Rel 16.0. We are executing a
    COBOL unload program that uses Fast/Access, a third party vendor
    product. The program ABENDs with the above error. If the program
    doesn't write the output to tape, the job executes successfully. The
    problem first occurred after we upgraded our tape library management
    system (CNTL-T from BMC). I opened a ticket with CA and they suggested
    that I check with the Fast/Access vendor, which I have, and I am still
    waiting to hear back from them. Any ideas? Thanks in advance.


    Mike Snipes
    USDA/OCFO/NFC
    New Orleans, La.
    "
    IDMS Public Discussion Forum
    IDMS-L@LISTSERV.IUASSN.COM
    SMTP
    IDMS-L@LISTSERV.IUASSN.COM
    IDMS-L@LISTSERV.IUASSN.COM
    SMTP








    Normal

    Normal
    Re: Fast/Access IDMSDBIO Error - 3031
    "No, we didn't. But that doesn't explain why Fast/Access is invoked and the job
    executes successfully when we write the output to dasd.

    Chris,

    The attributes of the output file remain the same, whether we write to tape or
    dasd. We also tried increasing the REGION parameter and the job failed with
    the same 3031 ABEND code.


    Mike S.
    IDMS-L@LISTSERV.IUASSN.COM@inter2 2/13/2007 11:24 AM >>>
    Did you upgrade to the latest Fast Access? We found when we migrated to R16
    we needed to upgrade to the Fast Access 8.0. (FASTAC 8.0 FAC080)

    I did a QW on ABND3031:

    Item ==> * MVS/QuickRef 6.4 * Col 1 Line 1 of
    7
    Command ==> Scroll ==>
    CSR
    You may scroll the information below UP, DOWN, LEFT, and/or RIGHT as needed

    ---------------- V=CA P=CA-IDMS MESSAGES R=R16 SP4 I=ABND3031
    ----------------
    ************ Text below copyright 2004 Computer Associates, Inc.
    *************
    ABND3031 3031



    Explanation: Unsupported return code from IDMSIOX2 user exit. Either the

    IDMSIOX2 is returning an incorrect return code, or the exit is linked with
    a
    version of IDMSDBIO that does not support the return code.



    Module: IDMSDBIO

    ****************************** BOTTOM OF DATA
    *******************************