View previous topic :: View next topic
|
Author |
Message |
thesumitk
Active User
Joined: 24 May 2013 Posts: 156 Location: INDIA
|
|
|
|
Hi,
When I was trying to recreate a scenario in test env which is repeating in production , I faced this issue .
A cobol Db2 program is abeding in production with Sqlcode -927 while When I compile it in my test library and run it goes fine .. I have tried it with bad input data and good data as well but it is not abendiing in test .. I think the problem is with PARMS are passed to DSNHPC when precompiling or to the IGYCRCTL but not yet sure about it .. I took the compile listing from production of the program and tried to math the compile option used with test but no luck..
When I run my job with production library it gets abend with SQLCODE -927 and when i compile -bind the same code in my test library it is going
fine . I have checked the DYNAM and NODYNAM option for compile they too looks fine since the program is compiled with NODYNAM option in production..
PLease suggest , Below is the definition of -927 code.
SQLCODE -927:
THE LANGUAGE INTERFACE (LI) WAS CALLED WHEN THE CONNECTING ENVIRONMENT WAS
NOT ESTABLISHED. THE PROGRAM SHOULD BE INVOKED UNDER THE DSN COMMAND
Explanation
In the TSO environment, the user has attempted to execute an application
program without first establishing the correct execution environment by
issuing the DSN command. In the IMS, CICS, or call attachment facility
(CAF) environment, the user has attempted to execute an application program
that is not using the correct language interface module.
Thanks
Sumit |
|
Back to top |
|
|
don.leahy
Active Member
Joined: 06 Jul 2010 Posts: 765 Location: Whitby, ON, Canada
|
|
|
|
If compiled with NODYNAM in production, check to see which flavour of DSNHLI was picked up at link edit time. Chances are that the wrong attachment facility (IMS, CICS, Call Attach, RRSAF and TSO are the usual choices) was used to link your program. |
|
Back to top |
|
|
thesumitk
Active User
Joined: 24 May 2013 Posts: 156 Location: INDIA
|
|
|
|
Thanks for your reply .. I just found in the Load Listing of the program is that the compiler option was used as NODYNM but if I see the link edit parm it says DYNAM in the dafault values for CICS release level ..
* ------Default CICS Release level------
CICSRLSE = '4.1' ;
CB2#PRM3 = ',OFFSET,MAP,DYNAM' ;
Is this the problem causing -927?
My program is not using CICS.
Thanks
Sumit |
|
Back to top |
|
|
thesumitk
Active User
Joined: 24 May 2013 Posts: 156 Location: INDIA
|
|
|
|
I dont know how I can check the flavour of DSNHLI but here is the info about DSNHLI which I found in load listing
EXTERNAL DSNHLI
NAME TYPE LENGTH DDNAME SEQ MEMBER
DSNAA * CSECT 108 SYSLIB 32 DSNHLI
DSNELI * CSECT 296 SYSLIB 32 DSNHLI
DSNWLI LABEL
DSNHLI LABEL
Please suggest how can I check the flavour of DSNHLI
Thanks
Sumit |
|
Back to top |
|
|
Dsingh29
Active User
Joined: 16 Dec 2008 Posts: 132 Location: IBM
|
|
Back to top |
|
|
thesumitk
Active User
Joined: 24 May 2013 Posts: 156 Location: INDIA
|
|
|
|
Hi Dave,
Thanks for the information !!
Actually I did see most of the posts related to -927 before posting mine one but the thing is that My scenario is bit diffrent where I am facing this issue only in production and not in TEST.I tried to map all the BIND options for test and prod but no luck however few option were diffrent in test but changing them couldnt rectify the problem , Load listing says that the program was compiled with NODYN option of Cobol in 2009 .One thing to consider here is that we migrated to extended version of DB2 after 2009 , I dont know if that can cause a problem?
I see in production and number of programs are runing as "PGM=DB2PGMNAME" so Should that be a problem when I am runing in same manner in test and getting RC=00?
Thanks
Sumit |
|
Back to top |
|
|
gylbharat
Active Member
Joined: 31 Jul 2009 Posts: 565 Location: Bangalore
|
|
|
|
Can you post the JCL? |
|
Back to top |
|
|
thesumitk
Active User
Joined: 24 May 2013 Posts: 156 Location: INDIA
|
|
|
|
Code: |
//JOBLIB DD DSN=TESTLT.LTC248A0.PROD.LOAD,DISP=SHR
// DD DSN=SYS7.DBATTACH.LOAD,DISP=SHR
// DD DSN=PRODLW.LOADLIB.CICS,DISP=SHR
// DD DSN=PRODLW.LOADLIB.BATCH,DISP=SHR
// DD DSN=D2D6.DB2.DSNEXIT,DISP=SHR
// DD DSN=SYS7.D2DG.SDSNLOAD,DISP=SHR
// DD DSN=SYS7.D2DG.RUNLIB.LOAD,DISP=SHR
//*JOBINCL INCLUDE MEMBER=DGIC&DB2SYS
//*
//PS130 EXEC PGM=LTC248A0
//*********************************************************************
//DBAIN DD DSN=TESTLT.CNTLCARD(LT248APN),DISP=SHR
//*LTRVALD DD DSN=TESTLT.SB740P00.SRTVALD.LT740740,DISP=SHR
//LTRVALD DD DSN=TESTLT.SB740P00.SRTVALD.LT740740.BKP,DISP=SHR
//COMPINDX DD DSN=TESTLT.SB240P00.COMPIND1.LT740740.D0521,DISP=SHR
// DD DSN=TESTLT.SB240P00.COMPIND2.LT740740(0),DISP=SHR
// DD DSN=TESTLT.SB240P00.COMPIND3.LT740740(0),DISP=SHR
// DD DSN=TESTLT.SB240P00.COMPIND4.LT740740(0),DISP=SHR
// DD DSN=TESTLT.SB240P00.COMPIND5.LT740740(0),DISP=SHR
// DD DSN=TESTLT.SB240P00.COMPIND6.LT740740(0),DISP=SHR
//ERFILE DD DSN=TESTLT.ERROR.FILE.OUT(+1),DISP=(NEW,CATLG,DELETE),
// DCB=(LRECL=44,RECFM=FB,DSORG=PS,BLKSIZE=0),
// SPACE=(CYL,(10,1),RLSE),UNIT=SYSDA
//SYSOUT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSABOUT DD SYSOUT=*
//SYSDBOUT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=* |
|
|
Back to top |
|
|
Marso
REXX Moderator
Joined: 13 Mar 2006 Posts: 1353 Location: Israel
|
|
|
|
A wild guess:
maybe you have to add to the JOBLIB:
Code: |
// DD DSN=SYS7.D2DG.DSNWLM,DISP=SHR |
|
|
Back to top |
|
|
thesumitk
Active User
Joined: 24 May 2013 Posts: 156 Location: INDIA
|
|
|
|
Thanks !!
But I do not have this lib in my system. no WLM libraries |
|
Back to top |
|
|
thesumitk
Active User
Joined: 24 May 2013 Posts: 156 Location: INDIA
|
|
|
|
In Addition to my last post
What I found today is that If the LInk Edit step contains below
//SYSIN DD *
INCLUDE SYSLIB(DSNELI)
then it blows down by -927
and if it contains
//SYSIN DD *
INCLUDE SYSLIB(IGZEBST)
then it is going fine
Any body have any idea about it pls? why it is like this?
Thanks
Sumit |
|
Back to top |
|
|
don.leahy
Active Member
Joined: 06 Jul 2010 Posts: 765 Location: Whitby, ON, Canada
|
|
|
|
DSNELI is the TSO attach facility. If you link DSNELI, then your program has to run under TSO. |
|
Back to top |
|
|
|