Bind failure

ratnakumar · New User Joined: 07 May 2009 Posts: 30 Location: Banglore

Hello,

I added logic to the existing CICS cobol db2 proram and moved the component to Endever. The component was successfully moved and gave the return code as zero. But if I check in the spool it says Bind was unsuccessful. At bind step RC is 12.

I am new to the CICS programing. So, I was checking with colleague and was told, If any modifications made to CICS cobol program we need to move corresponding map and macros the ED. Is that true? If yes, can anyone tell me how is that related.

- Ratna

dbzTHEdinosauer · Posted: Fri Aug 03, 2012 7:32 pm

probably because you did not move the dbrm.

was the bind failure part of the move,

or was the bind failure part of your original compilation of the program
at the previous endevor level?

or don't you know?

by the way, where is Banglore?

Pandora-Box · Posted: Fri Aug 03, 2012 7:59 pm

Bind failed with what reason?

Did you get any SQLCODE at the Bind step? ( Also Experts correct me if Endevour returns the SQLCODE while bind when failed)

@Dick

Banglore is a Capital of an Indian state Karnataka that city is also known as Silicon valley of India

dbzTHEdinosauer · Posted: Fri Aug 03, 2012 8:05 pm

ok, I thought it was spelled Bangalore,
or are there two cities or are both spellings acceptable?

ratnakumar · New User Joined: 07 May 2009 Posts: 30 Location: Banglore

The move to endevor test region was successful. I could see all components in Endevor test libraries (cobol code, CISC load, dbrm). So the DBRM is generated by ED and I believe ED should point to the DBRM location where it created.

And Bangalore is in India.

Pandora-Box · Posted: Fri Aug 03, 2012 8:15 pm

Bangalore,Banglore,Blr,Bangaluru all is accepted

Akatsukami · Posted: Fri Aug 03, 2012 8:15 pm

ratnakumar · New User Joined: 07 May 2009 Posts: 30 Location: Banglore

@Pandora-Box
I dont see any SQLCODE at the BIND STEP. It just gave me the bind return code as 12

ratnakumar · New User Joined: 07 May 2009 Posts: 30 Location: Banglore

@Pandora-Box

I just used the shortname for Endevor as ED. (what i usually refer with my colleagues).

Yes, I did checked and i see DBRM is generated by Endevor.

Actually, if i move a component to test in evdevor, it automatically compiles the program, generates the DBRM, Load lib and binds the component with DBRM generated.

I could do a manual bind, but am not sure what happens if i move the component in production (with bind failure in test region).

dbzTHEdinosauer · Posted: Fri Aug 03, 2012 8:42 pm

don"t want to be picky here, but:

the program is compiled at only one level - test.
the dbrm is also created here - output of pre-compiler.

as a module is promoted thru the different stages,
db2 programs are rebound - go thru a bind step
because each stage has its own db2 environment.

if the bind error occurs during the promotion process,
that means for some reason, the module was unable to successfully bind at the new level.

somewhere, someplace, the output of the promotion step is maintained.
within that output, contains the output generated by the bind step
and therein will you find the reason for the failure.

most endevor shops where i have worked maintain the spool output in the endevor LISTINGS ds.
(i can't remember how to get to that option,
but a little experimentation (or read the help for endevor)
and you can find it)
you will need to know the name of the LISTINGS ds for your project,
and to find that you will have to acquaint your self with the
documentation provided by your endevor support.

a typical reason for bind failure during promotion is
the table definition (DDL) at the next stage is not the same as that of the lower level.
this is often caused because the DDL has not been promoted to the next stage before the module.
or
as stated before,
the dbrm was not promoted.

now, if you are having a bind failure at the lowest stage (normally test)
then again the way to determine the problem is look at the LISTINGS ds.

one of the problems with the job that performs the GENERATION
(compile/link/bind)
of a module,
is that even though the bind fails,
the job requires an RC=0 inorder for the LISTINGS ds to be populated with the output.

a compile failure normally results in a JOB rc<>0
and as a result,
the spool output of the job is not migrated to the LISTINGS DS.

dbzTHEdinosauer · Posted: Sat Aug 04, 2012 9:13 am

ratnakumar,

before you ask any more questions,
answer ours:

1. what stage is the program?

2. you need to look at more than just the first dsid of the JOB.
you have to look-at the output created by the bind,
where there will indeed be an sql code
as well as other information why the bind failed.

3. Unless it is a DDL error,
you will have to make changes to your sql
and go thru the generation process of you module once again.

dick scherrer · Posted: Sat Aug 04, 2012 9:49 am

Hello,