Topic
  • 2 replies
  • Latest Post - ‏2006-02-25T14:02:49Z by SystemAdmin
SystemAdmin
SystemAdmin
3105 Posts

Pinned topic S0C1 abend on first SQL call

‏2006-02-24T21:18:00Z |
Can you please start me where I may find the reason I'm getting this problem.

Running a Cobol II/CICS/DB2 in z/OS. Everything compiles and links, but when I run the program in batch or using Compuware Xpediter, it goes out on the last CALL 'DSNHADDR' USING SQL-CODEPTR in the SQL-INITIAL procedure of the first DB2 call.

All I have to go by is this message:

DSN3201I - ABNORMAL EOT IN PROGRESS FOR USER=SDNAVAR 16
CONNECTION-ID=BATCH CORRELATION-ID= JOBNAME=SDNAVAR1
ASID=0080 TCB=009B9CF0

I have ran online CICS and batch non-CICS programs and they are working.

Appreciate any help.
Updated on 2006-02-25T14:02:49Z at 2006-02-25T14:02:49Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    3105 Posts

    Re: S0C1 abend on first SQL call

    ‏2006-02-25T00:05:46Z  
    In article
    <1496654933.1140815911222.JavaMail.wassrvr@ltsgwas007.sby.ibm.com>,
    jnavarra@dmc.org says...
    > Running a Cobol II/CICS/DB2 in z/OS. Everything compiles and links,
    > but when I run the program in batch or using Compuware Xpediter,
    > it goes out on the last CALL 'DSNHADDR' USING SQL-CODEPTR in the
    > SQL-INITIAL procedure of the first DB2 call.
    >

    Recompile with SSR and set a runtime option of CHECK(ON). The most likely
    cause for your abend0c1 is that some other part of your program has
    overlayed your working storage or your linkage section.

    Dougie Lawson
    IBM Farnborough, UK

    http://web.ukonline.co.uk/dougie.lawson
  • SystemAdmin
    SystemAdmin
    3105 Posts

    Re: S0C1 abend on first SQL call

    ‏2006-02-25T14:02:49Z  
    ?? Ursprüngliche Nachricht

    Am 24.02.06, 16:18:00, schrieb <jnavarra@dmc.org> zum Thema S0C1 abend
    on first SQL call:
    > Can you please start me where I may find the reason I'm getting this
    problem.

    > Running a Cobol II/CICS/DB2 in z/OS. Everything compiles and links,
    but when I run the program in batch or using Compuware Xpediter, it goes
    out on the last CALL 'DSNHADDR' USING SQL-CODEPTR in the SQL-INITIAL
    procedure of the first DB2 call.

    I think you must check your LINK. CICS is compiled with NODYNAM and
    you have to include the DB2.LINKLIB **after** the CICS Libs. DSNHLI
    must be then CICS version. DSNHADDR comes from DB2.
    For Batch you can set the compiler to DYNAM. But you have to put these
    steplibs in your jcl. In the following order :-)
    DL/1: IMS.RESLIB and then DB2.LOADLIB
    RUN DSN whit IKJEFT01: DB2.LOADLIB

    > All I have to go by is this message:

    > DSN3201I - ABNORMAL EOT IN PROGRESS FOR USER=SDNAVAR 16
    > CONNECTION-ID=BATCH CORRELATION-ID= JOBNAME=SDNAVAR1
    > ASID=0080 TCB=009B9CF0

    this only says: you are connectet to DB2. And the CICS Transaction
    Manager starts a two-phase-commit with rollback.

    > I have ran online CICS and batch non-CICS programs and they are
    working.

    > Appreciate any help.

    Einen schoenen Tag
    Andreas Lerch