Hello!  z/OS 1.4, DB2 7.1 here.    We got RRS up and running a few weeks 
ago and I'm making our first (1st) attempt to convert a COBOL SP from SPAS 
to WLM.    The only change I made was to modify the LinkEdit step to 
include 

        INCLUDE SYSLIB(DSNRLI)
        MODE AMODE(31) RMODE(ANY)

instead of  what we use for SPAS SP's:

        INCLUDE SYSLIB(DSNALI)
        MODE AMODE(31) RMODE(ANY)

I didn't make any other changes.  The WLM version starts and runs fine up 
until the first EXEC SQL statement, where it bombs with pretty much of a 
mess.   (The SP abends.  The WLM address space stays up and happy.) Our 
sysprog has raised an issue with IBM and I've created a CEEDUMP for the 
SP, but after a week, have gotten nowhere.  (Apparantly, this isn't the 
dump they want.)

Question for the group:   Is there any basic step I'm missing?    I'm not 
sure the problem is in DB2, so I'm cross-posting to IBM-Main. 

I'd love to solve this and not wrestle further with technical support, but 
am at a loss for ideas.  (I guess I should read the two or there redbooks 
I have relative to this topic, but have only perused them thus far.)

Thanks!

P.S.  For the thrill-seeker, here are excerpts from the stuff I sent our 
sysprog...

After multiple compiles and WLM refreshes, I'm stuck.  My comments are 
blue. 

The test can be done by anyone.  Type 

                TSO TSWOVDFT 

from a DSYS connected TSO session to recreate.  This runs a RExx that 
calls the SP.  You should see:

=========================================================================================

*** BEFORE THE CALL ***
OVDFT_PGM_NAME        : TSWOVDFT
DISPLAY_SW            : X
SP_STATUS             : 0
UPDATE_SW             : Y
CICS_SW               : Y
DEBUG_SW              :
DOC_CODE              : BA
DOC_ID                : '954029          '
ERROR DIAGNOSTICS
SQLCODE:  -430
SQLSTATE:  38503
SQLERRMC: PROCEDURE:DBATEST .FIW_OVERDRAFTS    :DBATEST .FIW_OVERDRAFTS :
SQLERRP:  DSNX9WAC
I=1 SQLERRD(I): 0       I=2 SQLERRD(I): 0       I=3 SQLERRD(I): 0 I=4 
SQLERRD(I): -1
I=5 SQLERRD(I): 0       I=6 SQLERRD(I): 0       I=1 SQLWARN(I): I=2 
SQLWARN(I):
I=3 SQLWARN(I): I=4 SQLWARN(I): I=5 SQLWARN(I): I=6 SQLWARN(I):
I=7 SQLWARN(I): I=8 SQLWARN(I): I=9 SQLWARN(I): I=10 SQLWARN(I):
DSNT408I SQLCODE = -430, ERROR:    (SPECIFIC NAME ) HAS ABNORMALLY 
TERMINATED
 DSNT415I SQLERRP    =  SQL PROCEDURE DETECTING ERROR

*** AFTER THE CALL ***
OVDFT_PGM_NAME        : TSWOVDFT
DISPLAY_SW            : X
SP_STATUS             : 0
UPDATE_SW             : Y
CICS_SW               : Y
DEBUG_SW              :
DOC_CODE              : BA
DOC_ID                : '954029          '
DISCONNECT RC:  -1
DISCONNECT SQLCODE:  -924
ERROR DIAGNOSTICS
SQLCODE:  -924
SQLSTATE:  58006
SQLERRMC: 00000001:0000000C:00F30020
SQLERRP:  DSNTZALI
I=1 SQLERRD(I): 0       I=2 SQLERRD(I): 0       I=3 SQLERRD(I): 0 I=4 
SQLERRD(I): 0
I=5 SQLERRD(I): 0       I=6 SQLERRD(I): 0       I=1 SQLWARN(I): I=2 
SQLWARN(I):
I=3 SQLWARN(I): I=4 SQLWARN(I): I=5 SQLWARN(I): I=6 SQLWARN(I):
I=7 SQLWARN(I): I=8 SQLWARN(I): I=9 SQLWARN(I): I=10 SQLWARN(I):
DSNT408I SQLCODE = -924, ERROR:  DB2 CONNECTION INTERNAL ERROR, , ,
 DSNT415I SQLERRP    =  SQL PROCEDURE DETECTING ERROR
===========================================
==============================================

===========================================
==============================================
The Stored Procedure does fire.  The DBT1APP1 address space starts up and 
the COBOL DISPLAY statements confirm that FIWOVDFT it makes it as far as 
the first DB2 EXEC SQL (SELECT) statment.
===========================================
==============================================
FIWOVDFT - ENTERED: 05/10/2007 13.41.05 COMPILED: 05/10/07  13.39.35

FIWOVDFT BEFORE PARMS:
FIZ-PGM-NAME       TSTOVDFT
FIZ-DISPLAY        Y
FIZ-SP-STATUS      000000000
FIZ-UPDATE-SW      Y
FIZ-CICS-SW        Y
FIZ-DEBUG
FIZ-DOC-CODE       BA
FIZ-DOC-ID         954029
WS-DOC-CODE:       BA
WS-DOC-ID:         954029
PREPARING TO RETRIEVE TIMESTAMP
CEE3204S The system detected a protection exception (System Completion 
Code=0C4).
         From compile unit FIWOVDFT at entry point FIWOVDFT at compile 
unit offset -F39E9FA8 at entry offset -F39E9FA8
          at address 000A0000.
===========================================
==============================================
There doesn't seem to be anything else useful displayed in DBT1APP1. 
However, in DBT1MSTR
the following shows up:
===========================================
==============================================
13.41.06 STC06107  DSNX905I  -DBT1 DSNX9CAC PROCEDURE OR FUNCTION  494
   494             DBATEST .FIW_OVERDRAFTS     TERMINATED ABNORMALLY ASID= 
0047 WLM_ENV=
   494             DBT1APP1
13.41.06 STC06107  DSN3201I  -DBT1 ABNORMAL EOT IN PROGRESS FOR  495
   495             USER=DB2WLM CONNECTION-ID=RRSAF CORRELATION-ID=
   495             JOBNAME=DBT1APP1 ASID=0047 TCB=00AC6B68

=========================================================================================

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to