|
View previous topic :: View next topic
|
| Author |
Message |
Abhinav Chandra
New User
Joined: 13 Oct 2012
Posts: 29
Location: India
|
|
|
|
Ran the job with rebind package successfully but still getting bind issue when the module rebinded in the rebind package job is referred in the other job.
What will be the possible cause of this.
Log generated is as -
| Code: |
DSNT254I :DB2R DSNTBRB2 REBIND OPTIONS FOR
PACKAGE = DB2R.MLCV1A0B.IM2ABCD.()
ACTION
OWNER MLQV1A0B
QUALIFIER MLQV1A0B
VALIDATE BIND
EXPLAIN YES
ISOLATION CS
RELEASE
COPY
DSNT255I :DB2R DSNTBRB2 REBIND OPTIONS FOR
PACKAGE = DB2R.MLCV1A0B.IM2ABCD.()
SQLERROR NOPACKAGE
CURRENTDATA NO
DEGREE 1
DYNAMICRULES BIND
DEFER
REOPT NONE
KEEPDYNAMIC NO
IMMEDWRITE NO
DBPROTOCOL DRDA
OPTHINT
ENCODING EBCDIC(00037)
ROUNDING HALFEVEN
PATH
DSNT232I :DB2R SUCCESSFUL REBIND FOR
PACKAGE = DB2R.MLCV1A0B.IM2ABCD.() |
Here module IM2ABCD was rebinded successfully, but when referred later in the other job it abended with bind issue.
Code'd |
|
| Back to top |
|
 |
Akatsukami
Global Moderator
Joined: 03 Oct 2009
Posts: 1788
Location: Bloomington, IL
|
|
|
|
| It abended? That's too bad! If only you had told us how it abended -- abend code, SQL code, DB2 reason code, and messages -- we might have been able to help. |
|
| Back to top |
|
|
Abhinav Chandra
New User
Joined: 13 Oct 2012
Posts: 29
Location: India
|
|
|
|
Actually the rebind was successful for the same module. But later when the same module was referred in another job then it got abended due to bind issue and the log for the abended job was -
| Code: |
DSNT408I SQLCODE = -805, ERROR: DBRM OR PACKAGE NAME DB2R..IM2ABCD.197C79AA0
2ED646 NOT FOUND IN PLAN MLPV1A0B. REASON 03
DSNT418I SQLSTATE = 51002 SQLSTATE RETURN CODE
DSNT415I SQLERRP = DSNXEPM SQL PROCEDURE DETECTING ERROR
DSNT416I SQLERRD = -251 0 0 -1 0 0 SQL DIAGNOSTIC INFORMATION
DSNT416I SQLERRD = X'FFFFFF05' X'00000000' X'00000000' X'FFFFFFFF'
X'00000000' X'00000000' SQL DIAGNOSTIC INFORMATION |
Code'd |
|
| Back to top |
|
|
Akatsukami
Global Moderator
Joined: 03 Oct 2009
Posts: 1788
Location: Bloomington, IL
|
|
|
|
| The contoken (X'197C79AA02ED646') corresponds to a timestamp of 2013-08-30-16.16.41.438041 UTC. Unless you're just getting around to seeking help after a month, your load module was linked with the wrong version of IM2ABCD. Check the libraries concatenated to the various DDs used as sources for static routines in your link-edit, or as sources for dynamic routines in the execution JCL. Use AMBLIST to distinguish the compile if there are multiple copies of IM2ABCD. |
|
| Back to top |
|
|
Abhinav Chandra
New User
Joined: 13 Oct 2012
Posts: 29
Location: India
|
|
|
|
Thanks for your prompt response.
Use AMBLIST to distinguish the compile if there are multiple copies of IM2ABCD -- How to do this ? |
|
| Back to top |
|
|
Akatsukami
Global Moderator
Joined: 03 Oct 2009
Posts: 1788
Location: Bloomington, IL
|
|
|
|
Set up and execute an AMBLIST job:
| Code: |
//JS10 EXEC PGM=AMBLIST
//SYSPRINT DD SYSOUT=*
//SYSLIB DD DSN=a load library,DISP=SHR
//SYSIN DD *
LISTIDR MEMBER=load module
/* |
You will get output similar to this (for a load module in my sandbox load library):
| Code: |
CEESTART 5655-W67 42.00 2013/163
CEEMAIN 5655-W67 42.00 2013/163
****M471 5655-W67 42.00 2013/163
****M472 5655-W67 42.00 2013/163
CEEBETBL 569623400 01.06 2011/077
CEEOPIPI 569623400 01.06 2011/077
CEEPMATH 569623400 01.06 2011/077
CEESG003 569623400 01.06 2011/077
CEEBLLST 569623400 01.06 2011/077
CEEBTRM 569623400 01.06 2011/077
CEEBPUBT 569623400 01.06 2011/077
CEEROOTA 569623400 01.06 2011/077
PL/X-390 02.04 2011/077
CEEP#INT 569623400 01.06 2011/077
PL/X-390 02.04 2011/077
CEEP#CAL 569623400 01.06 2011/077
PL/X-390 02.04 2011/077
CEEP#TRM 569623400 01.06 2011/077
PL/X-390 02.04 2011/077
CEEARLU 569623400 01.06 2011/077
PL/X-390 02.04 2011/077
CEEBINT 569623400 01.06 2011/077
PL/X-390 02.04 2011/077
CEEBPIRA 569623400 01.06 2011/077
PL/X-390 02.04 2011/077
CEECPYRT 569623400 01.06 2011/077
PL/X-390 02.04 2011/077
IBMQBRCG 569623400 01.06 2011/074
IBMQEFSH 569623400 01.06 2011/074
IBMQDNPE 569623400 01.06 2011/074
IBMQOFOP 569623400 01.06 2011/074
IBMPINPL 569623400 01.06 2011/074
CEESG011 569623400 01.06 2011/074 |
Find the source name (IM2ABCD) in the leftmost column; the date (which may be sufficient) is in the rightmost column. |
|
| Back to top |
|
|
Abhinav Chandra
New User
Joined: 13 Oct 2012
Posts: 29
Location: India
|
|
|
|
what does the below mentioned fields implies -
| Code: |
CSECT TRANSLATOR VR.MD YR/DY
IM2ABCD 5655S7100 41.00 2013/242 |
Code'd |
|
| Back to top |
|
|
Akatsukami
Global Moderator
Joined: 03 Oct 2009
Posts: 1788
Location: Bloomington, IL
|
|
|
|
| Abhinav Chandra wrote: |
what does the below mentioned fields implies -
CSECT TRANSLATOR VR.MD YR/DY
IM2ABCD 5655S7100 41.00 2013/242 |
CSECT: Control Section; for current purposes the name of the source module.
TRANSLATOR: The compiler, etc. used to produce the object module. A list of translator names and codes is here. 5655S7100 is the Enterprise COBOL compiler, Version 4.
VR.MD: The version, release, and modification information, Version 4.1 of the compiler was used.
YR/DY: The ordinal (often miscalled "Julian") date the module was compiled. The 242st day of 2013 was 30 August.
Unless IM2ABCD was compiled multiple times that day, this is the correct load module. |
|
| Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
The Translatior column is telling you the product (compiler in this case) used to create the object code. If you google for COBOL and that code you'll come to this, which is a useful reference for that AMBLIST output.
You could also find the documentation for AMBLIST from IBM, and it describes the report output. Once you know it is a product code, it is easy to find out what it is for, and find out that you already know what it is telling you in this case. Enterprise COBOL 4.1.
The final column is the Julian date of the translation (compile in your case).
That one is a month or so old. |
|
| Back to top |
|
|
Abhinav Chandra
New User
Joined: 13 Oct 2012
Posts: 29
Location: India
|
|
|
|
| Thanks Akatsukami for being on top of the issue. |
|
| Back to top |
|
|
Abhinav Chandra
New User
Joined: 13 Oct 2012
Posts: 29
Location: India
|
|
|
|
| Thanks Bill Woodger !! |
|
| Back to top |
|
|
|
|
