IBM Support

PK47893: ADDING A RESILIENT DATA SERVER ADMINISTRATIVE TASK SCHEDULER

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • ADDING A RESILIENT DATA SERVER ADMINISTRATIVE TASK SCHEDULER
    
    DB2MIGV9/K  DB2MIGV8/K
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of the DB2 scheduler for           *
    *                 administrative tasks. All users of the       *
    *                 stored procedures ADMIN_INFO_SSID or         *
    *                 ADMIN_COMMAND_DB2.                           *
    ****************************************************************
    * PROBLEM DESCRIPTION: The DB2 administrative enablement, in   *
    *                      particuliar the DB2 administrative      *
    *                      scheduler, is not available for DB2     *
    *                      V8.1 for z/OS. In addition, the         *
    *                      interface for the scheduler does not    *
    *                      suit the need for a common scheduling   *
    *                      function on all IBM data servers.       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This PTF is shipped to update the DB2 administrative enablement
    interface, including the administrative scheduler. The update
    contains a partly new interface and bug fixes. This PTF also
    delivers those features back into DB2 for z/OS Version 8.
    For more information on these features, refer to the sections
    "Scheduling administrative tasks", "The ADMIN_COMMAND_DB2
    stored procedure", and "The ADMIN_INFO_SSID stored procedure"
    in the DB2 V8.1 or V9.1 for z/OS Administration manual.
    

Problem conclusion

Temporary fix

Comments

  • You need to install this PTF if you are already a user of the
    DB2 scheduler for administrative tasks or of the administrative
    enablement stored procedures named above.
    
    WARNING: do not apply the PTF before adapting any site-provided
             callers of routines changed by this PTF, i.e.
             SYSPROC.ADMIN_TASK_SCHEDULE, SYSPROC.ADMIN_TASK_REMOVE,
             DSNADM.ADMIN_TASK_LIST, and DSNADM.ADMIN_TASK_STATUS.
             In particuliar, users of the Optimization Service
             Center, which uses the scheduler, have to make sure
             that they have a version compatible with the new
             interface.
    
    
    What's new in DB2 V9.1 for z/OS
    ===============================
    (1) The scheduler interface changed to be compatible with the
        interface on other IBM data server. The following changes
        have been implemented:
         - The stored procedure SYSPROC.ADMIN_TASK_SCHEDULE is
           renamed to ADMIN_TASK_ADD.
         - The output parameter TASK_ID in stored procedure
           SYSPROC.ADMIN_TASK_ADD is replaced by the INOUT
           parameter TASK_NAME of type VARCHAR(128). The user can
           name the tasks instead of getting an index for them.
           the names "DB2STOP", "DB2START" and all strings
           beginning with "TASK_ID_" are reserved.
         - The input parameter TRIGGER_TASK_ID in stored procedure
           SYSPROC.ADMIN_TASK_ADD is replaced by the input
           parameter TRIGGER_TASK_NAME of type VARCHAR(128). The
           values 0 and -1 of this parameter are replaced by the
           string values "DB2STOP" and "DB2START" respectively.
         - The input parameter TASK_ID in stored procedure
           SYSPROC.ADMIN_TASK_REMOVE is also replaced by an input
           parameter TASK_NAME of type VARCHAR(128).
         - The two table UDFs DSNADM.ADMIN_TASK_LIST and
           DSNADM.ADMIN_TASK_STATUS return a column TASK_NAME
           of type VARCHAR(128) instead of the column TASK_ID.
         - The table UDF DSNADM.ADMIN_TASK_LIST return a column
           TRIGGER_TASK_NAME of type VARCHAR(128) instead of the
           column TRIGGER_TASK_ID.
         - The table UDF function DSNADM.ADMIN_TASK_STATUS returns
           the value UNKNOWN in column STATUS when the scheduler
           was stopped before this task terminates its execution.
         - The table UDF function DSNADM.ADMIN_TASK_STATUS returns
           a new additional column SQLERRMC of type VARCHAR(70)
           containing the value SQLERRMC of executing a stored
           procedure. It is similar to the other column SQLCODE,
           SQLSTATE and SQLERRP.
    (2) The scheduler startup in DB2 has been modified:
         - The scheduler is now started after RRSAF is started.
           This change eliminates console message DSNA679I during
           normal startup of the scheduler with DB2.
         - When the scheduler cannot be started, a new error
           message DSNA650I is written on the console instead of
           message DSNI002I.
    (3) The scheduler behavior changed:
         - After executing a stored procedure, even in case of
           errors, the scheduler will COMMIT. This replaces the
           ROLLBACK that was executed in the previous version, and
           this is compatible with the scheduler behavior on other
           IBM data servers.
         - The messages DSNA681I and DSNA682I are not written to
           the console any more when the inconsistencies in the
           two task lists can be solved. The messages DSNA681I and
           DSNA683I are still written when the inconsistencies
           cannot be resolved.
         - When a task list cannot be accessed, the message
           DSNA679I is still written to the console. A more detailed
           information is given in this message. When the task
           list becomes available, the new message DSNA695I is now
           written to the console.
           In addition, a new parameter ERRFREQ allows to set up
           the minimum frequency (in minutes) where the message
           DSNA679I is written to the console when a task list
           cannot be accessed. If not indicated, the message is
           written once per minute.
           You can define the parameter ERRFREQ in the scheduler
           started task similarly to the other parameters. You can
           also modify this parameter dynamically with the
           following command:
           modify dsnadmt,appl=errfreq=60
           where dsnadmt is the name of the scheduler and with the
           desired frequency instead of 60.
    (4) Different bugs have been fixed, for example the scheduler
        now can connect to subsystem whose ID is less than 4
        characters long.
    
     In addition, following DB2 installation jobs are modified:
    
     -DSNTIJSG: DDL is addded and modified to take the interface
                changes into account.
     -DSNTIJDE: Now contains an additional AMS DELETE statement to
                discard prefix.TASKLIST, the VSAM data set for the
                administrative scheduler task list.  Note: DSNTIJDE
                is an optional job for scrapping a partially-
                installed DB2 subsystem.  Do not run this job
                during migration or fallback.
     -DSNTIJFV: Now contains statements for fallback handling of the
                administrative scheduler address space proc
                (ssnmADMT).
    
    
    What's new in DB2 V8.1 for z/OS
    ===============================
    (1) The stored procedures SYSPROC.ADMIN_INFO_SSID and
        SYSPROC.ADMIN_COMMAND_DB2 have been added. They are
        similar to the stored procedures in DB2 V9.1 for z/OS.
    (2) The scheduler for administrative tasks has been added.
        It is similar to the scheduler in DB2 V9.1 for z/OS
        after applying this PTF.
        If you want to schedule tasks with this scheduler, make
        sure that you use z/OS v1.7 or higher.
    (3) The stored procedure DSNWZP is now defined with option
        READS SQL.
    
     In addition, following DB2 installation jobs are modified:
     -DSNTIJMV: Now creates the address space proc (default name
                DSNADMT) for the administrative scheduler started
                task.  This proc should be renamed ssnmADMT where
                ssnm is the name of the DB2 subsystem. For DB2
                data sharing, each member of the group requires
                its own ssnmADMT proc, where ssnm is the name of
                the DB2 subsystem.
     -DSNTIJUZ: Now contains a new subsystem parameter, ADMTPROC,
                under DSN6SPRM in job step DSNTIZA that specifies
                a name for the JCL procedure that is used to start
                the DB2 administrative scheduler.  See the note
                for DSNTIJMV above for the naming convention of
                the address space proc. A null value for ADMTPROC
                is allowed, in which case no DB2 administrative
                scheduler will be associated with the DB2
                subsystem. The default setting for ADMTPROC is
                DSNADMT. In data sharing, this job needs to be
                customized and run for each member of the group.
     -DSNTIJIN: Now contains an additional job step, DSNTADM, that
                defines prefix.TASKLIST, the VSAM data set for the
                administrative scheduler task list. In data sharing,
                this data set is shared by all members of the group
                so needs to be defined only once, when installing or
                migrating the first member of the group.
     -DSNTIJDE: Now contains an additional AMS DELETE statement to
                discard prefix.TASKLIST, the VSAM data set for the
                administrative scheduler task list.  Note: DSNTIJDE
                is an optional job for scrapping a partially-
                installed DB2 subsystem.  Do not run this job
                during migration or fallback.
     -DSNTIJSG: Now contains an additional job step, DSNTIAS, that
                creates a database, a table space, and tables plus
                stored procedures and functions in support of the
                administrative enablement, including
                administrative scheduler.  This step also binds the
                packages for the new stored procs and functions.
                Statements are added to step DSNTIJG to grant access
                to the new tables, routines, and packages. In data
                sharing, these objects needs to be created and bound
                only once,  when installing or migrating the first
                member of the group.
     -DSNTIJRA: A new job for setting up the system security
                environment for the administrative scheduler.  In
                data sharing, this job needs to be customized and
                run for each member of the group.
    
     This PTF also modifies DB2 installation CLIST member DSNTINS1
     to reflect the changes to jobs DSNTIJMV, DSNTIJIN, and
     DSNTIJSG. The CLIST currently does not tailor job DSNTIJRA.
    
    ž**** PE08/04/08 PTF IN ERROR. SEE APAR PK63288  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PK47893

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    810

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-06-27

  • Closed date

    2007-12-07

  • Last modified date

    2011-12-01

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UK32046 UK32047

Modules/Macros

  • ADMTCOMM ADMTDEF  ADMTMSG  ADMTPCOM ADMTREQ
    DSN@DMCD DSN@DMTA DSN@DMTL DSN@DMTR DSN@DMTS DSN@DMTU DSN@ZP
    DSN@6DB2 DSN@6THP DSNADMA0 DSNADMCD DSNADMH1 DSNADMIS DSNADMJ4
    DSNADMMG DSNADMMW DSNADMSH DSNADMSM DSNADMTA DSNADMTF DSNADMTI
    DSNADMTL DSNADMTM DSNADMTP DSNADMTR DSNADMTS DSNADMTT DSNADMTU
    DSNADMTY DSNADMT2 DSNA6BUF DSNA6DB2 DSNA6DMN DSNA6HAI DSNA6HB2
    DSNA6HCH DSNA6HHD DSNA6HHJ DSNA6HHP DSNA6HI  DSNA6HMN DSNA6HSA
    DSNA6HTL DSNA6HUF DSNA6II  DSNA6IPC DSNA6ITK DSNA6MAI DSNA6MVS
    DSNA6SCH DSNA6THD DSNA6THJ DSNA6THP DSNA6TRC DSNA6UTL DSNA6VSA
    DSNCIM   DSNCIMX  DSNDGMC  DSNDQWPZ DSNDSPRM DSNFADIR DSNFADTA
    DSNFMDIR DSNTIJDE DSNTIJFV DSNTIJIN DSNTIJMV DSNTIJRA DSNTIJSG
    DSNTIJUZ DSNTINST DSNTINS1 DSNTINS2 DSNWZP   DSNYSTRT DSNZOVTB
    DSN6SPCK DSN6SPRM DSN7ILML DSN7SINI HDB8810J HDB9910J
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • R810 PSY UK32046

       UP07/12/27 P F712

  • R910 PSY UK32047

       UP07/12/22 P F712

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 December 2011