DB2 bind on z/os

BIND and REBIND options for packages and plans

There are several options you can use for binding or rebinding plans and packages. Some of the options are common for both bind and rebind and for both plans and packages.

Defaults: The default for an option is the value used if you omit the entire option.

  • A default of plan value for BIND PACKAGE means that the default is the same as the value determined during the bind or rebind of the plan to which the package is appended at run time.
  • A default of existing value for REBIND PLAN or REBIND PACKAGE means that the default is the value that was determined during the previous bind or rebind of the plan or package that you are rebinding.

Catalog records: The DB2® catalog records information about plans and packages, chiefly in the tables SYSIBM.SYSPLAN and SYSIBM.SYSPACKAGE. The descriptions of where the options record information omit the constant qualifier, SYSIBM, of those table names.

For all other cases, the option descriptions note the specific defaults, which DB2 assigns at bind time. If a specific default value exists, that value is underlined.

    • ACQUIRE bind option
      The ACQUIRE bind option specifies
      that resources for the packages in the plan are to be acquired when
      the application first accesses them.
    • ACTION bind option
      The ACTION option determines whether the object (plan or
      package) replaces an existing object with the same name or is new.
    • APCOMPARE bind option
      The APCOMPARE option determines whether the new access paths are different from the older
      access paths.
    • APPLCOMPAT bind option
      The APPLCOMPAT option specifies the package compatibility
      level behavior for static SQL.
    • APRETAINDUP bind option
      The APRETAINDUP option determines whether or not DB2 retains an old package copy
      when access paths of the old copy are identical to the incoming copy.
    • APREUSE bind option
      The APREUSE option specifies whether DB2 tries to
      reuse previous access paths for SQL statements in a package. DB2 uses
      information about the previous access paths from the directory to create
      a hint.
    • ARCHIVESENSITIVE bind option
      The ARCHIVESENSITIVE option determines whether references to archive-enabled tables in
      both static and dynamic SQL statements are affected by the value of the SYSIBMADM.GET_ARCHIVE global
      variable.
    • BUSTIMESENSITIVE bind option
      The BUSTIMESENSITIVE option determines whether references
      to application-period temporal tables in both static and dynamic SQL
      statements are affected by the value of the CURRENT TEMPORAL BUSINESS_TIME
      special register.
    • CACHESIZE bind option
      The CACHESIZE option determines the size (in bytes) of
      the authorization cache acquired in the EDM pool for the plan.
    • COLLID bind option
      The COLLID option specifies that any DBRMs in the plan
      are to be bound to packages.
    • CONCURRENTACCESSRESOLUTION bind option
      The CONCURRENTACCESSRESOLUTION option specifies which concurrent
      access resolution option to use for statements in a package.
    • COPY bind option
      The COPY option copies an existing package, and names that
      package.
    • CURRENTDATA bind option
      The CURRENTDATA option determines whether to require data
      currency for read-only and ambiguous cursors when the isolation level
      of cursor stability is in effect. It also determines whether block
      fetching can be used for distributed, ambiguous cursors.
    • CURRENTSERVER bind option
      The CURRENTSERVER option determines the location to connect
      to before running a plan.
    • DBPROTOCOL bind option
      The DBPROTOCOL option
      specifies the protocol to be used when connecting to a remote site.
    • DEFER and NODEFER bind options
      The DEFER and NODEFER options determine whether to defer
      preparation for dynamic SQL statements that refer to remote objects,
      or to prepare them immediately.
    • DEGREE bind option
      The DEGREE option determines whether to attempt to run
      a query using parallel processing to maximize performance.
    • DEPLOY bind option
      The DEPLOY option deploys
      a non-inline SQL function or a native SQL procedure.
    • DESCSTAT bind option
      The DESCSTAT option determines whether DB2 builds a DESCRIBE SQL descriptor area (SQLDA)
      when binding static SQL statements.
    • DISCONNECT bind option
      The DISCONNECT option determines which remote connections
      to destroy during commit operations.
    • DYNAMICRULES bind option
      The DYNAMICRULES option determines the rules that apply
      at run time for certain dynamic SQL attributes.
    • ENABLE and DISABLE bind options
      The ENABLE and DISABLE options determines which connections
      can use a plan or package.
    • ENCODING bind option
      The ENCODING option specifies the application encoding
      for all host variables in static statements in a plan or package.
    • EXPLAIN bind option
      The EXPLAIN option causes the bind
      process to obtain information about how SQL statements in the package
      or packages are to execute.
    • EXTENDEDINDICATOR bind option
      The EXTENDEDINDICATOR option determines whether DB2 recognizes extended indicator
      variables when the associated package is run.
    • FILTER bind option
      The FILTER option lets you delete a set of queries in the
      SYSIBM.SYSQUERY table under a {tag} value that is specified by the
      SYSQUERY.USERFILTER column.
    • FLAG bind option
      The FLAG option determines the messages to display during
      the bind process.
    • GENERIC bind option
      The GENERIC option specifies one or more bind options that
      are supported by the target server, but are not supported as options
      for BIND PACKAGE or REBIND PACKAGE on the DB2 for z/OS® subsystem
      on which the BIND or REBIND command is issued.
    • GETACCELARCHIVE bind option
      The GETACCELARCHIVE bind option specifies whether a static
      SQL query that is bound for acceleration retrieves archived data on
      the accelerator, instead of active data.
    • IMMEDWRITE bind option
      The IMMEDWRITE option indicates whether immediate writes
      are to be done for updates that are made to group buffer pool dependent
      page sets or partitions.
    • ISOLATION bind option
      The ISOLATION option determines how far to isolate an application
      from the effects of other running applications.
    • KEEPDYNAMIC bind option
      The KEEPDYNAMIC option determines whether DB2 keeps dynamic SQL statements after commit points. .
    • LIBRARY bind option
      The LIBRARY option determines what
      partitioned data set or zFS file path to search for the DBRM that
      is listed in the MEMBER option.
    • MEMBER bind option
      The MEMBER option determines
      what database request modules (DBRMs) to include in the package.
    • OPTHINT bind option
      The OPTHINT option controls whether access paths that are
      specified in PLAN_TABLE instances are used for static SQL statements.
    • OPTIONS bind option
      The OPTIONS option specifies which bind options to use
      for the new package when the COPY option is specified.
    • OWNER bind option
      The OWNER option determines the authorization ID of the
      owner of a plan or package.
    • PACKAGE bind option
      The PACKAGE option determines the packages to bind or rebind.
    • PATH bind option
      The PATH option determines the SQL path that DB2 uses to resolve unqualified stored procedure
      names in CALL statements, in user-defined data types, and in functions.
    • PATHDEFAULT bind option
      The PATHDEFAULT option resets the
      PATH value for a package or plan to SYSIBM, SYSFUN, SYSPROC, SYSIBMADM, plan
      qualifier
      , or to SYSIBM, SYSFUN, SYSPROC, SYSIBMADM, package
      qualifier
      .
    • PKLIST and NOPKLIST bind options
      The PKLIST option determines the packages to include in
      a package list. The NOPKLIST option deletes packages from a package
      list.
    • PLAN bind option
      The PLAN option determines the plan or plans to bind or rebind.
    • PLANMGMT bind option
      The PLANMGMT option retains, during a rebind operation,
      all relevant package information (such as metadata, query text, dependencies,
      authorizations, and access paths) in catalog tables and in the directory.
    • PROGAUTH bind option
      The PROGAUTH option specifies whether DB2 performs program authorization checking to
      determine whether DB2 can execute
      a plan.
    • QUALIFIER bind option
      The QUALIFIER option determines the implicit qualifier
      for unqualified names of tables, views, indexes, and aliases contained
      in the plan or package.
    • QUERYACCELERATION bind option
      The QUERYACCELERATION bind option specifies whether a static
      SQL query is bound for acceleration, and if so, with what behavior.
    • QUERYID bind option
      The QUERYID option frees entries in the SYSIBM.SYSQUERY
      table, and the SYSIBM.SYSQUERYPLAN table or the SYSIBM.SYSQUERYOPTS
      table.
    • RELEASE bind option
      The RELEASE option determines when to release resources
      that a program uses, either at each commit point or when the program
      terminates.
    • REOPT bind option
      The REOPT option specifies whether DB2 determines an access path at run time by
      using the values of host variables, parameter markers, and special
      registers.
    • ROUNDING bind option
      The ROUNDING option specifies the rounding mode at bind
      time. Use rounding mode to manipulate DECFLOAT data.
    • SQLERROR bind option
      The SQLERROR option determines whether to create a package
      if SQL errors occur.
    • SQLRULES bind option
      The SQLRULES option determines whether you can execute
      a type 2 CONNECT statement to an existing SQL connection, according
      to DB2 rules.
    • SWITCH bind option
      The SWITCH option causes the previous copy or original
      copy of a package to become the current copy of the package.
    • SYSTIMESENSITIVE bind option
      The SYSTIMESENSITIVE option specifies whether references
      to system-period temporal tables in both static and dynamic SQL statements
      are affected by the value of the CURRENT TEMPORAL SYSTEM_TIME special
      register.
    • VALIDATE bind option
      The VALIDATE option determines whether to recheck, at run
      time, errors of the types "OBJECT NOT FOUND" and "NOT AUTHORIZED"
      that are found during bind or rebind.
时间: 2024-08-02 09:05:34

DB2 bind on z/os的相关文章

【翻译自mos文章】Oracle GoldenGate 对IBM大型机 z/OS 2.1 和DB2 v11的支持

GoldenGate 对IBM大型机 z/OS 2.1 和DB2 v11的支持 来源于: GoldenGate Support for z/OS 2.1 and DB2 v11 (文档 ID 1941364.1) 适用于: Oracle GoldenGate - Version 12.1.2.1.2 and later Information in this document applies to any platform. 目标: 需要知道是否有一个GoldenGate版本能支持 IBM大型机

IBM z/OS 简介

因为有幸获得IBM的面试机会,先提前了解一下这个了不起的操作系统. z/OS是IBM研发的用于大型机的64位操作系统.第一次亮相是在2000年的10月份.z/OS支持IBM的很多服务,像我们熟知的DB2和WebSphere.也支持64位的java,C,C++和UNIX APIs.The Open Group将其视为一种UNIX操作系统,文件系统采用HFS和zFS.可以直接通过TCP/IP通信,支持常用的http服务,像FTP,NFS等. 有人问,在一对一的对决中,UNIX和z/OS,who胜?

IBM Z/OS 操作系统学习笔记(持续更新)

存储管理子系统(DFSMS) 存储管理也是系统的一项基本服务. 系统存储管理子系统(Storage Management System,SMS)定义了系统中的各种输入/输出设备,并控制这些设备的操作:同时,它还提供文件系统的基本功能,使用户可以方便.快速地访问数据.系统的各种程序及数据都保存在硬盘上,如果希望执行某些程序,必须用到存储管理的服务,因此,SMS一般先于其他子系统启动,以提供基本的存储管理服务. 存储管理软件组件(Data Facility Storage Management Su

z/OS上Dataset 的移动

最近的一个需求,需要把大批量的Dataset移到新的Storage Class,新的Volume中去,刚开始感觉非常头疼.仔细研究后发现这个事情其实很简单.确实符合别人所说,事情的在你真正开始努力之后就会变简单了.   首先创建你的target Storage class和Storage Group,并把相关的Volume加到对于的SG,这时候不需要担心现有的Vol上已经存在的Dataset,改动Storage Group不会删除DataSet.   然后配置ACS Routines,将HLQ,

Index on DB2 for z/OS: DB2 for z/OS 的索引

可以创建在任何表上的索引: Unique Index:An index that ensures that the value in a particular column or set of columns is unique. Primary index:A unique index on the primary key of the table. Secondary index:An index that is not a primary index. Clustering index:A

[转帖]新一代IBM Z14主机技术介绍

新一代IBM Z14主机技术介绍 https://cloud.tencent.com/developer/news/268909 IBM最新的已经有IBM Z15 主机了.. 文章来源:企鹅号 - 云间设备e线 编者按:随着我行业务的稳步推进,特别是近来互联网业务的发展与金融市场的活跃,我行的核心生产主机系统的交易负载和核心数据库存储规模与日俱增,核心业务交易量呈现迅猛的增长趋势,需要处理能力强大.安全.稳定.可靠的IT基础架构予以支撑.除此之外,为应对新增业务.特殊业务和临时需求带来的不可预期

DB2操作

第一章DB2开发基础 在进行DB2应用开发之前,了解DB2应用程序的结构,掌握相关概念,设置开发环境是很必要的.本章主要介绍这几个方面的内容. 1.1 DB2应用程序开发概述 1.1.1 程序结构 DB2应用程序包括以下几个部分: 1.声明和初始化变量 2.连接到数据库 3.执行一个或者多个事务 4.与数据库断开连接 5.结束程序 一个事务是一组数据库操作,在提交给数据库之前,必须确认完全成功执行.在嵌入式SQL应用程序中,当应用程序成功地连接到一个数据库时,一个事务就自动开始了,结束于执行一条

你搞懂 ORACLE、 SQLSERVER、MYSQL与DB2的区别了吗

ORACLE. SQLSERVER.MYSQL与DB2的区别--平台性:    Oracle.MYSQL与DB2可在所有主流平台上运行:    SQL Server只能在Windows下运行: --安全性:    Oracle的安全认证获得最高认证级别的ISO标准认证,而SQL Server并没有获得什么安全认证:    这方面证明了Oracle的安全性是高于SQL Server的: --数据类型.函数.sql语句:    oracle中有复合数据类型,sql server中没有: 总之:   

DB2常用命令小结

PS:执行命令前需要进入DB2的账户下:su db2inst1 修改密码:更改相应的操作系统密码即可,windows上可以更改db2admin的密码,linux上更改db2inst1的密码即可,db2 的数据库密码是和操作系统绑定的,就像大家说的只需要修改操作系统上用户的密码就可以了.你想改那个用户的密码你就在操作系统上改那个用户的密码. DB2 linux 下安装配置教程 ===============================经验最宝贵=========================