Antwort: Re: [DB2-L] Antwort: Re: [DB2-L] Multiple COUNTs With Distinct DB2 ZOS V7

Roy Boxwell

Antwort: Re: [DB2-L] Antwort: Re: [DB2-L] Multiple COUNTs With Distinct DB2 ZOS V7
Hi Raj!

The ROSHARE column is an "old" column in SYSDATABASE and is no longer
used (It disappeared in V6 by the way). It came from the good old days
when you could define a database
as being Read Only for the local DB2 but "shared" to other remote DB2s.

ROSHARE
Indicates how the database will be shared using shared read-only data.
If ROSHARE is omitted, the database will not be shared. For an explanation
of shared read-only data, see
Appendix F (Volume 2) of Administration Guide.

OWNER The database will be shared, and the current server will be
the DB2 that can update the database.

READ The current server is to have read-only access to the
database through shared read-only data.



A strange concept that never really took off and was then buried by DRDA,
DDF and Data Sharing.

Roy Boxwell
SOFTWARE ENGINEERING GMBH
-Product Development-
Robert-Stolz-Strasse 5
40470 Duesseldorf/Germany
Tel. +49 (0)211 96149-0
Fax +49 (0)211 96149-35
E-mail [login to unmask email]
Homepage www.seg.de

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Brian Bear

DB2 zOS v7
(in response to Roy Boxwell)
Fellow listers.

I am struggling with privileges for Bind.

Zparms "BIND NEW PACKAGE" is BINDADD.
PUBLIC has been granted PACKADM and CREATE in collection 'PRODTEST'.

When a developer BINDs to package PRODTEST, they receive
DSNT235I - DSNTBCM2 BIND AUTHORIZATION ERROR
USING APPL319 AUTHORITY
PACKAGE = DB2SYSA.PRODTEST.APIV3CMM.()
PRIVILEGE = BINDADD

Additionally, it's not all developers, just some.

No one has SYSADM or SYSCTRL or BINDADD.

The manual says that with zparm "BIND NEW PACKAGE" as BINDADD, that I
must also grant BINDADD to allow additions/modifications to the
collection. But this is apparently not the case for those developers
that are able to successfully bind.

Any suggestions?

Thanks in advance.

Brian Bear
Charming Shoppes.

*****************************************************************************
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you
received this message in error, please contact the sender and delete
the material from any computer.
*****************************************************************************

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

James Campbell

Re: DB2 zOS v7
(in response to Brian Bear)
"Specify whether BIND or BINDADD authority is required to bind a new
version of an existing package. If you accept the default, BINDADD, you
allow only users with the BINDADD system privilege to create a new
package." And, as some ids (such as APPL319) don't have BINDADD, ...

I can see "GRANT BINDADD TO <developers>" coming on.

James Campbell

On 5 Dec 2006 at 16:30, Bear, Brian wrote:

> Fellow listers.
>
> I am struggling with privileges for Bind.
>
> Zparms "BIND NEW PACKAGE" is BINDADD.
> PUBLIC has been granted PACKADM and CREATE in collection 'PRODTEST'.
>
> When a developer BINDs to package PRODTEST, they receive
> DSNT235I - DSNTBCM2 BIND AUTHORIZATION ERROR
> USING APPL319 AUTHORITY
> PACKAGE = DB2SYSA.PRODTEST.APIV3CMM.()
> PRIVILEGE = BINDADD
>
> Additionally, it's not all developers, just some.
>
> No one has SYSADM or SYSCTRL or BINDADD.
>
> The manual says that with zparm "BIND NEW PACKAGE" as BINDADD, that I
> must also grant BINDADD to allow additions/modifications to the
> collection. But this is apparently not the case for those developers
> that are able to successfully bind.
>
> Any suggestions?
>
> Thanks in advance.
>
> Brian Bear
> Charming Shoppes.
>
> *****************************************************************************
> The information transmitted is intended only for the person or entity to
> which it is addressed and may contain confidential and/or privileged
> material. Any review, retransmission, dissemination or other use of, or
> taking of any action in reliance upon, this information by persons or
> entities other than the intended recipient is prohibited. If you
> received this message in error, please contact the sender and delete
> the material from any computer.
> *****************************************************************************
>
> ---------------------------------------------------------------------------------
> Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Raymond Bell

Re: DB2 zOS v7
(in response to James Campbell)
Ah, John, I do love a good dose of sarcasm in the morning. Keep it coming;
keeps me sharp(ish).


Raymond Bell
DBA Coming Down From a) a night on the turps, b) a big meal out, c) sod-all
sleep and d) having to turn up at work today and actually do some. Until
I'm outsourced, of course. Oh, wait, I already am! I'm a Kiwi working in
the UK! Hmmm, not sure if that counts...

-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On Behalf
Of James Campbell
Sent: 06 December 2006 00:48
To: [login to unmask email]
Subject: Re: [DB2-L] DB2 zOS v7

"Specify whether BIND or BINDADD authority is required to bind a new version
of an existing package. If you accept the default, BINDADD, you allow only
users with the BINDADD system privilege to create a new package." And, as
some ids (such as APPL319) don't have BINDADD, ...

I can see "GRANT BINDADD TO <developers>" coming on.

James Campbell

On 5 Dec 2006 at 16:30, Bear, Brian wrote:

> Fellow listers.
>
> I am struggling with privileges for Bind.
>
> Zparms "BIND NEW PACKAGE" is BINDADD.
> PUBLIC has been granted PACKADM and CREATE in collection 'PRODTEST'.
>
> When a developer BINDs to package PRODTEST, they receive DSNT235I -
> DSNTBCM2 BIND AUTHORIZATION ERROR
> USING APPL319 AUTHORITY
> PACKAGE = DB2SYSA.PRODTEST.APIV3CMM.()
> PRIVILEGE = BINDADD
>
> Additionally, it's not all developers, just some.
>
> No one has SYSADM or SYSCTRL or BINDADD.
>
> The manual says that with zparm "BIND NEW PACKAGE" as BINDADD, that I
> must also grant BINDADD to allow additions/modifications to the
> collection. But this is apparently not the case for those developers
> that are able to successfully bind.
>
> Any suggestions?
>
> Thanks in advance.
>
> Brian Bear
> Charming Shoppes.
>
> **********************************************************************
> ******* The information transmitted is intended only for the person or
> entity to which it is addressed and may contain confidential and/or
> privileged material. Any review, retransmission, dissemination or
> other use of, or taking of any action in reliance upon, this
> information by persons or
> entities other than the intended recipient is prohibited. If you
> received this message in error, please contact the sender and delete
> the material from any computer.
> **********************************************************************
> *******
>
> ----------------------------------------------------------------------
> ----------- Welcome to the IDUG DB2-L list. To unsubscribe, go to the
> archives and home page at
> http://www.idugdb2-l.org/archives/db2-l.html. From that page select
> "Join or Leave the list". The IDUG DB2-L FAQ is at
> http://www.idugdb2-l.org. The IDUG List Admins can be reached at
> [login to unmask email] Find out the latest on IDUG
> conferences at http://conferences.idug.org/index.cfm

----------------------------------------------------------------------------
-----
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org.
The IDUG List Admins can be reached at [login to unmask email] Find
out the latest on IDUG conferences at http://conferences.idug.org/index.cfm


This e-mail (and any attachments) may contain privileged and/or confidential information. If you are not the intended recipient please do not disclose, copy, distribute, disseminate or take any action in reliance on it. If you have received this message in error please reply and tell us and then delete it. Should you wish to communicate with us by e-mail we cannot guarantee the security of any data outside our own computer systems. For the protection of Legal & General's systems and staff, incoming emails will be automatically scanned.

Any information contained in this message may be subject to applicable terms and conditions and must not be construed as giving investment advice within or outside the United Kingdom.

The following companies are subsidiary companies of the Legal & General Group Plc which are authorised and regulated by the Financial Services Authority for advising and arranging the products shown: Legal & General Partnership Services Limited (insurance and mortgages), Legal & General Insurance Limited (insurance), Legal & General Assurance Society Limited
(life assurance, pensions and investments), Legal & General Unit Trust Managers Limited and Legal & General Portfolio Management Services Limited (investments).

They are registered in England under numbers shown.
The registered office is Temple Court, 11 Queen Victoria Street, London EC4N 4TP.

Legal & General Partnership Services Limited: 5045000 Legal & General Assurance Society Limited: 166055 Legal & General (Unit Trust Managers) Limited: 1009418 Legal & General (Portfolio Management Services) Limited: 2457525 Legal & General Insurance Limited: 423930

They are registered with the Financial Services Authority under numbers shown. You can check this at www.fsa.gov.uk/register

Legal & General Partnership Services Limited: 300792 Legal & General Assurance Society Limited: 117659 Legal & General (Unit Trust Managers) Limited: 119273 Legal & General (Portfolio Management Services) Limited: 146786 Legal & General Insurance Limited: 202050

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Brian Bear

Re: DB2 zOS v7
(in response to Raymond Bell)
Understood. But doesn't explain how others are able to bind when they
don't have BINDADD atuh. I'll keep poking around I guess.

Thanks for the reply.

Brian.

-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email]
Sent: Tuesday, December 05, 2006 7:48 PM
To: [login to unmask email]
Subject: Re: [DB2-L] DB2 zOS v7






"Specify whether BIND or BINDADD authority is required to bind a new
version of an existing package. If you accept the default, BINDADD, you
allow only users with the BINDADD system privilege to create a new
package." And, as some ids (such as APPL319) don't have BINDADD, ...

I can see "GRANT BINDADD TO <developers>" coming on.

James Campbell

On 5 Dec 2006 at 16:30, Bear, Brian wrote:

> Fellow listers.
>
> I am struggling with privileges for Bind.
>
> Zparms "BIND NEW PACKAGE" is BINDADD.
> PUBLIC has been granted PACKADM and CREATE in collection 'PRODTEST'.
>
> When a developer BINDs to package PRODTEST, they receive DSNT235I -
> DSNTBCM2 BIND AUTHORIZATION ERROR
> USING APPL319 AUTHORITY
> PACKAGE = DB2SYSA.PRODTEST.APIV3CMM.()
> PRIVILEGE = BINDADD
>
> Additionally, it's not all developers, just some.
>
> No one has SYSADM or SYSCTRL or BINDADD.
>
> The manual says that with zparm "BIND NEW PACKAGE" as BINDADD, that I
> must also grant BINDADD to allow additions/modifications to the
> collection. But this is apparently not the case for those
developers
> that are able to successfully bind.
>
> Any suggestions?
>
> Thanks in advance.
>
> Brian Bear
> Charming Shoppes.
>
>
************************************************************************
*****

> The information transmitted is intended only for the person or entity
> to which it is addressed and may contain confidential and/or
> privileged material. Any review, retransmission, dissemination or
> other use of, or taking of any action in reliance upon, this
information by persons or
> entities other than the intended recipient is prohibited. If you
> received this message in error, please contact the sender and delete
> the material from any computer.
>
************************************************************************
*****

>
>
------------------------------------------------------------------------
---------

> Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that
page select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at http://conferences.idug.org/index.cfm

------------------------------------------------------------------------
---------

Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that
page select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

James Campbell

Re: DB2 zOS v7
(in response to Brian Bear)
GRANT BINDADD TO YYY
BIND PACKAGE(...) OWNER(YYY)
?

James Campbell

On 6 Dec 2006 at 9:32, Bear, Brian wrote:

> Understood. But doesn't explain how others are able to bind when they
> don't have BINDADD atuh. I'll keep poking around I guess.
>
> Thanks for the reply.
>
> Brian.
>
> -----Original Message-----
> From: DB2 Data Base Discussion List [mailto:[login to unmask email]
> Sent: Tuesday, December 05, 2006 7:48 PM
> To: [login to unmask email]
> Subject: Re: [DB2-L] DB2 zOS v7
>
>
>
>
>
>
> "Specify whether BIND or BINDADD authority is required to bind a new
> version of an existing package. If you accept the default, BINDADD, you
> allow only users with the BINDADD system privilege to create a new
> package." And, as some ids (such as APPL319) don't have BINDADD, ...
>
> I can see "GRANT BINDADD TO <developers>" coming on.
>
> James Campbell
>
> On 5 Dec 2006 at 16:30, Bear, Brian wrote:
>
> > Fellow listers.
> >
> > I am struggling with privileges for Bind.
> >
> > Zparms "BIND NEW PACKAGE" is BINDADD.
> > PUBLIC has been granted PACKADM and CREATE in collection 'PRODTEST'.
> >
> > When a developer BINDs to package PRODTEST, they receive DSNT235I -
> > DSNTBCM2 BIND AUTHORIZATION ERROR
> > USING APPL319 AUTHORITY
> > PACKAGE = DB2SYSA.PRODTEST.APIV3CMM.()
> > PRIVILEGE = BINDADD
> >
> > Additionally, it's not all developers, just some.
> >
> > No one has SYSADM or SYSCTRL or BINDADD.
> >
> > The manual says that with zparm "BIND NEW PACKAGE" as BINDADD, that I
> > must also grant BINDADD to allow additions/modifications to the
> > collection. But this is apparently not the case for those
> developers
> > that are able to successfully bind.
> >
> > Any suggestions?
> >
> > Thanks in advance.
> >
> > Brian Bear
> > Charming Shoppes.
> >
> >
> ************************************************************************
> *****
>
> > The information transmitted is intended only for the person or entity
> > to which it is addressed and may contain confidential and/or
> > privileged material. Any review, retransmission, dissemination or
> > other use of, or taking of any action in reliance upon, this
> information by persons or
> > entities other than the intended recipient is prohibited. If you
> > received this message in error, please contact the sender and delete
> > the material from any computer.
> >
> ************************************************************************
> *****
>
> >
> >
> ------------------------------------------------------------------------
> ---------
>
> > Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
> home page at http://www.idugdb2-l.org/archives/db2-l.html. From that
> page select "Join or Leave the list". The IDUG DB2-L FAQ is at
> http://www.idugdb2-l.org. The IDUG List Admins can be reached at
> [login to unmask email] Find out the latest on IDUG conferences
> at http://conferences.idug.org/index.cfm
>
> ------------------------------------------------------------------------
> ---------
>
> Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
> home page at http://www.idugdb2-l.org/archives/db2-l.html. From that
> page select "Join or Leave the list". The IDUG DB2-L FAQ is at
> http://www.idugdb2-l.org. The IDUG List Admins can be reached at
> [login to unmask email] Find out the latest on IDUG conferences
> at http://conferences.idug.org/index.cfm
>
> ---------------------------------------------------------------------------------
> Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Ruediger Kurtz

AW: [DB2-L] DB2 zOS v7
(in response to James Campbell)
Might "BINDAGENT" be the reason ?

Ruediger

-----Ursprüngliche Nachricht-----
Von: DB2 Data Base Discussion List [mailto:[login to unmask email] Im Auftrag von Bear, Brian
Gesendet: Mittwoch, 6. Dezember 2006 15:33
An: [login to unmask email]
Betreff: Re: [DB2-L] DB2 zOS v7

Understood. But doesn't explain how others are able to bind when they
don't have BINDADD atuh. I'll keep poking around I guess.

Thanks for the reply.

Brian.

-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email]
Sent: Tuesday, December 05, 2006 7:48 PM
To: [login to unmask email]
Subject: Re: [DB2-L] DB2 zOS v7






"Specify whether BIND or BINDADD authority is required to bind a new
version of an existing package. If you accept the default, BINDADD, you
allow only users with the BINDADD system privilege to create a new
package." And, as some ids (such as APPL319) don't have BINDADD, ...

I can see "GRANT BINDADD TO <developers>" coming on.

James Campbell

On 5 Dec 2006 at 16:30, Bear, Brian wrote:

> Fellow listers.
>
> I am struggling with privileges for Bind.
>
> Zparms "BIND NEW PACKAGE" is BINDADD.
> PUBLIC has been granted PACKADM and CREATE in collection 'PRODTEST'.
>
> When a developer BINDs to package PRODTEST, they receive DSNT235I -
> DSNTBCM2 BIND AUTHORIZATION ERROR
> USING APPL319 AUTHORITY
> PACKAGE = DB2SYSA.PRODTEST.APIV3CMM.()
> PRIVILEGE = BINDADD
>
> Additionally, it's not all developers, just some.
>
> No one has SYSADM or SYSCTRL or BINDADD.
>
> The manual says that with zparm "BIND NEW PACKAGE" as BINDADD, that I
> must also grant BINDADD to allow additions/modifications to the
> collection. But this is apparently not the case for those
developers
> that are able to successfully bind.
>
> Any suggestions?
>
> Thanks in advance.
>
> Brian Bear
> Charming Shoppes.
>
>
************************************************************************
*****

> The information transmitted is intended only for the person or entity
> to which it is addressed and may contain confidential and/or
> privileged material. Any review, retransmission, dissemination or
> other use of, or taking of any action in reliance upon, this
information by persons or
> entities other than the intended recipient is prohibited. If you
> received this message in error, please contact the sender and delete
> the material from any computer.
>
************************************************************************
*****

>
>
------------------------------------------------------------------------
---------

> Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that
page select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at http://conferences.idug.org/index.cfm

------------------------------------------------------------------------
---------

Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that
page select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Sysdba AHE

Re: DB2 zOS v7
(in response to Ruediger Kurtz)
Brian,

Maybe there's confusion about the words "a new version of an existing
package" quoted from the manual, which means "a package with a new version
number". A BIND with ACTION(REPLACE) for an existing package doesn't need
BINDADD - the restriction is only on creating a new package.

Your example indicates that you're not using versioning (version number is
null), so could it be that the BINDs that work are actually replacing
existing packages?

Hope this helps

Neil Price
TNT Express, UK

---------------------------------------------------------------------------------------------------------------
This message and any attachment are confidential and may be privileged or otherwise protected from disclosure.
If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system.
If you are not the intended recipient you must not copy this message or attachment or disclose the contents to any other person.
---------------------------------------------------------------------------------------------------------------

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Brian Bear

Re: AW: [DB2-L] DB2 zOS v7
(in response to Sysdba AHE)
OMG, that's it!!!

Got to revoke that immediately. Yikes.

Thanks a bunch.

-----Original Message-----
From: Kurtz [mailto:Kurtz]
Sent: Thursday, December 07, 2006 2:25 AM
To: [login to unmask email]
Subject: [DB2-L] AW: [DB2-L] DB2 zOS v7






Might "BINDAGENT" be the reason ?

Ruediger

-----Ursprüngliche Nachricht-----
Von: DB2 Data Base Discussion List [mailto:[login to unmask email] Im Auftrag von Bear, Brian
Gesendet: Mittwoch, 6. Dezember 2006 15:33
An: [login to unmask email]
Betreff: Re: [DB2-L] DB2 zOS v7

Understood. But doesn't explain how others are able to bind when they don't have BINDADD atuh. I'll keep poking around I guess.

Thanks for the reply.

Brian.

-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email]
Sent: Tuesday, December 05, 2006 7:48 PM
To: [login to unmask email]
Subject: Re: [DB2-L] DB2 zOS v7






"Specify whether BIND or BINDADD authority is required to bind a new version of an existing package. If you accept the default, BINDADD, you allow only users with the BINDADD system privilege to create a new package." And, as some ids (such as APPL319) don't have BINDADD, ...

I can see "GRANT BINDADD TO <developers>" coming on.

James Campbell

On 5 Dec 2006 at 16:30, Bear, Brian wrote:

> Fellow listers.
>
> I am struggling with privileges for Bind.
>
> Zparms "BIND NEW PACKAGE" is BINDADD.
> PUBLIC has been granted PACKADM and CREATE in collection 'PRODTEST'.
>
> When a developer BINDs to package PRODTEST, they receive DSNT235I -
> DSNTBCM2 BIND AUTHORIZATION ERROR
> USING APPL319 AUTHORITY
> PACKAGE = DB2SYSA.PRODTEST.APIV3CMM.()
> PRIVILEGE = BINDADD
>
> Additionally, it's not all developers, just some.
>
> No one has SYSADM or SYSCTRL or BINDADD.
>
> The manual says that with zparm "BIND NEW PACKAGE" as BINDADD, that I
> must also grant BINDADD to allow additions/modifications to the
> collection. But this is apparently not the case for those
developers
> that are able to successfully bind.
>
> Any suggestions?
>
> Thanks in advance.
>
> Brian Bear
> Charming Shoppes.
>
>
************************************************************************
*****

> The information transmitted is intended only for the person or entity
> to which it is addressed and may contain confidential and/or
> privileged material. Any review, retransmission, dissemination or
> other use of, or taking of any action in reliance upon, this
information by persons or
> entities other than the intended recipient is prohibited. If you
> received this message in error, please contact the sender and delete
> the material from any computer.
>
************************************************************************
*****

>
>
------------------------------------------------------------------------
---------

> Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

------------------------------------------------------------------------
---------

Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------

Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------

Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm