PK63288: NEW INTERFACE FOR THE DB2 ADMINISTRATIVE TASK SCHEDULER 08/04/08 PTF PECHANGE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• This APAR supersedes the apar PK47893 and PTF UK32047. There is
  no code error but the ++HOLD for the PTF was wrong and must be
  corrected in this APAR. All sources delivered in the previous
  APAR are delivered in this APAR again.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 9 for z/OS users that make use of    *
  *                 the DB2 scheduler for administrative tasks.  *
  ****************************************************************
  * PROBLEM DESCRIPTION: PTF UK32047 has a wrong ++HOLD text.    *
  *                      The interface of the DB2 scheduler      *
  *                      for administrative tasks does not suit  *
  *                      the need for a common scheduling        *
  *                      function on all IBM data servers.       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This PTF supersedes PTF UK32047 that contains a wrong ++HOLD
  text.
  
  This PTF is shipped to update the DB2 administrative scheduler.
  The update contains a partly new interface and bug fixes.
  For more information on the scheduler, refer to the section
  "Scheduling administrative tasks" in the DB2 V9.1 for z/OS
  Administration manual.
  
  WARNING: do not apply the PTF without 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.
  

Problem conclusion

• 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 returns 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 the parameter ERRFREQ is 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).
  

Temporary fix

Comments

APAR Information

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

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

  UK36794

Modules/Macros

• ADMTCOMM ADMTDEF  ADMTMSG  ADMTPCOM DSN@DMTA
  DSN@DMTL DSN@DMTR DSN@DMTS DSN@DMTU DSN@6DB2 DSN@6THP DSNADMMG
  DSNADMMW DSNADMTA DSNADMTI DSNADMTL DSNADMTM DSNADMTP DSNADMTR
  DSNADMTS DSNADMTU DSNA6BUF DSNA6DB2 DSNA6DMN DSNA6HB2 DSNA6HUF
  DSNA6II  DSNA6IPC DSNA6ITK DSNA6MAI DSNA6SCH DSNA6THD DSNA6THJ
  DSNA6THP DSNCIM   DSNFADIR DSNFADTA DSNFMDIR DSNTIJDE DSNTIJFV
  DSNTIJIN DSNTIJSG DSNTINS1 DSNTINS2 DSNYSTRT DSN6SPRM DSN7SINI
  HDB9910J
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• R910 PSY UK36794

     UP08/06/13 P F806 

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.