|
View previous topic :: View next topic
|
| Author |
Message |
Susanta
Active User
Joined: 17 Nov 2009
Posts: 126
Location: India
|
|
|
|
| If i compile a program with auto bind option in endevor and if compilation is successful , then how can I know whether the bind also successful ?[/i] |
|
| Back to top |
|
 |
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
| Quote: |
AUTO BIND field (ABIND subsystem parameter)
The ABIND subsystem parameter determines whether plans or packages are to be automatically rebound (or autobound) at run time in certain situations.
Automatic rebinds can improve availability and administration of plans and packages because you do not need to explicitly rebind some plans and packages. However, automatic rebinds can also hinder performance because they require access to the DB2® directory and catalog.
Acceptable values: YES, NO, COEXIST
Default: YES
Update: option 15 on panel DSNTIPB
DSNZPxxx: DSN6SPRM ABIND
YES
Allows automatic rebind operations to be performed at run time when a plan or package meets one of the following criteria:
It is not valid; the VALID column of SYSPLAN or SYSPACKAGE contains "N".
It was last bound in DB2 Version 9.1, but it is now running on a previous version of DB2.
This autobind is performed on the previous version of DB2 because that is where the user is attempting to run the plan or package. This autobind is performed only for the first attempt to run the plan or package on DB2 Version 8.
It was last autobound on DB2 Version 8, but it is now running again on DB2 Version 9.1.
This Version 8-to-Version 9.1 autobind is performed on DB2 Version 9.1 because that is where the user is attempting to run the plan or package. This autobind is performed only for the first attempt to run the plan or package on Version 9.1 after an autobind on Version 8. If the plan or package is later run again on DB2 Version 8, the autobind process starts again as previously described.
NO
Prevents DB2 from performing automatic rebind operations under any circumstances. This means that when any of the following conditions are true, you must explicitly rebind the plan or package before it can be run again:
You want to run a plan or package that is not valid; the VALID column of SYSPLAN or SYSPACKAGE contains "N".
You are attempting to run a plan or package on a previous version that was last bound (explicitly or automatically) in DB2 Version 9.1.
You are attempting to run a plan or package on DB2 Version 9.1 for which DB2 last performed an autobind. If AUTO BIND = NO has always been in effect on Version 8, then the autobind might not have been done previously on Version 8.
If you attempt to run any plan or package on DB2 Version 9.1 in one of the situations described above, you receive SQLCODE -908 SQLSTATE 23510.
|
as You see the auto bind is not related to the build stage
( whatever tool is being used SCLM CHANGEMAN or ENDEVOR )
You should be able to see the result of the build looking at the output of the job
or using the facility of ENDEVOR |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
| Quote: |
| with auto bind option in endevor |
if you mean that the JCL generated to pre-compile/compile/link/bind a db2 program indeed attempts to BIND at the end of the linkage editor step,
then it depends on your site.
I have worked at sites that precluded the negative results of a bind operation to be reflected in the return code of the job or the step.
in that case I had to manually look at the sysout of the bind step to insure all binds were successful.
an unsuccessful bind was also not reflected in the RC of the endevor displays.
this was inconvenient, but the dba's wanted it that way and it was not going to change.
that meant that you had to look at the output of your job. |
|
| Back to top |
|
|
Susanta
Active User
Joined: 17 Nov 2009
Posts: 126
Location: India
|
|
|
|
| That means I need to check the bindsteps return code to get to know whether bind successfull or not. I think i am clear now... Thanks Dick . |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
| Quote: |
| check the bindsteps return code |
not if your site is set-up like the one I to which I was referring.
If the bindstep return code was non-zero, then the Job return code would also be non-zero.
you need to look at the sysout generated by the BIND and look for the key word SUCCESSFUL. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
it means that You have to ask Your support!
all depends on how the build process was setup!
a proper setup will tell the step at which the error occurred
to find the error You wiil have in any case to see the listing with the step invoilved! |
|
| Back to top |
|
|
Susanta
Active User
Joined: 17 Nov 2009
Posts: 126
Location: India
|
|
|
|
I have found that the bind sysout shows "dbrm stored successfully", as dick pointed out, I never used to see this sysout earlier..
Many Thanks Enricho and Dick, |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
| Quote: |
| dbrm stored successfully |
since the dbrm is generated by the pre-compiler, and storing the dbrm successfully would be a result of an endevor action,
this is not what you need to determine if the bind was successful. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
The BIND is after the compile/link sysouts. |
|
| Back to top |
|
|
|
|
