When is the authorization check on DB2 objects done - at
BIND time or run time?
Answer / shyam
In the Plans or packages which has the Static SQL's,
Authorization check is done based on the VALIDATE parameter
in BIND control card ..If VALIDATE(BIND), Authorization
check is done during the BIND time. If VALIDATE(RUN),
Authorization check is done during the run time.
For the plans or packages having Dynamic SQL's ,
Authorization check is done during the run time.
Shyam
| Is This Answer Correct ? | 16 Yes | 1 No |
Can we update view in db2?
What is database manager in db2?
what are the copybook changes generally we done?can anyone tell me......... Thanks in advance........
SET is the ANSI standard for variable assignment, SELECT is not. SET can only assign one variable at a time, SELECT can make multiple assignments at once. If assigning from a query, SET can only assign a scalar value. If the query returns multiple values/rows then SET will raise an error. SELECT will assign one of the values to the variable and hide the fact that multiple values were returned (so you'd likely never know why something was going wrong elsewhere - have fun troubleshooting that one) When assigning from a query if there is no value returned then SET will assign NULL, where SELECT will not make the assignment at all (so the variable will not be changed from it's previous value) As far as speed differences - there are no direct differences between SET and SELECT. However SELECT's ability to make multiple assignments in one shot does give it a slight speed advantage over SET.
Is it possible using max on a char column?
Suppose there are many duplicate records in a Db2 table. What is the query to retrive only duplicate records?
What is the syntax for FETCH in DB2 ?
insert into tablename a column1, column2 select column1, column2 from tablename b i am getting abend -104..can any one help?
How to find last record before record through SQLRPGLE?
i want to maintain uniqueness on pdf without make lf??????????
What is the use of predicate?
My cobol program(not having any sql statements) is calling another cobol program ( having sql statements), what is needed for compilation and run in jcls .