PRIVATE_PROTOCOL in macro DSN6FAC

Private protocol is no longer supported; however, this subsystem parameter controls package EXECUTE authorization behavior related to remote DB2® requester applications.

When a remote DB2 requester application accesses the server DB2 subsystem through DRDA protocol, a plan owner is associated with the remote DB2 requester application plan. For packages that are executed as part of this plan by a remote DB2 requester application using DRDA protocol, the PRIVATE_PROTOCOL parameter has the following effects. This parameter is online updatable, and valid values are NO and AUTH.

Start of change NO indicates that when a remote DB2 requester application accesses the DB2 subsystem through DRDA protocol, package EXECUTE authority must be explicitly granted at this subsystem. The authority must be granted to the primary ID or an associated secondary ID for packages that the requester application executes as part of the plan End of change

Start of change AUTH indicates that when a remote DB2 requester application accesses the DB2 subsystem through DRDA protocol, package EXECUTE authority must be explicitly granted to the plan owner at this subsystem. This plan owner must have EXECUTE authority at this subsystem for packages that the requester application executes as part of the plan. The plan owner needs no other privilege to execute the package. End of change

Start of change The default value for PRIVATE_PROTOCOL is NO. End of change