A fix is available
APAR status
Closed as program error.
Error description
DB2 Administration Tool allows user to build CHECK DATA job by filling in parameters in panel ADB2USK for EXCEPTION DELETE and LOG parameters. . If user pf3 exits from CHECK DATA job, pf3'g past panel ADB2USK without blanking out the EXCEPTION DELETE and LOG parameters, then attempts to use DB2 Object Compare Tool in the same Admin session to build a drop/create scenario, and panel GOC5 parm to generate a CHECK DATA utility is set to YES, the OC job will fail rc20 with errors similar to: . FUNCTION = GOCGAJOB, LINE 5676: FTINCL GOCTCHK RC = 20 ZERRMSG = ISPF107 ZERRSM = Control word error ZERRLM = Invalid control word parameter, ADB2USKO record-110 . If user logs out of Admin and logs back in to start a new session, then runs the same OC scenario, the OC job completes rc0. However, the CHECK DATA control statement contains invalid syntax, and running the APPLY job fails rc08 in CHECK DATA utility with errors similar to: . DSNU050I DSNUGDFL - CHECK DATA TABLESPACE SPPT.SPPCPRD SORTDEVT SYSDA SORTNUM 4 DELETE YES LOG YES ERRDDN( UTLERR) WORKDDN(UTLUT1,SORTOUT) DSNU071I DSNUGDFL - KEYWORD 'DELETE' REQUIRES KEYWORD 'FOR EXCEPTION'
Local fix
Blank out or delete ADB2USK parms when finished generating CHECK DATA utility job.
Problem summary
**************************************************************** * USERS AFFECTED: Users of the DB2 Administration Tool for * * z/OS and DB2 Object Comparison Tool * * for z/OS. * **************************************************************** * PROBLEM DESCRIPTION: The error MSGDSNU071I KEYWORD * * 'DELETE' REQUIRES KEYWORD * * 'FOR EXCEPTION' ON CHECK DATA * * UTILITY occurs when generating * * a CHECK FOR EXCEPTION and then * * running a compare using CHECK. * * Incorrect CHECK syntax is observed * * when the DELETE option is YES * * but no exception is used. * **************************************************************** * RECOMMENDATION: * **************************************************************** A failure occurs when generating a CHECK FOR EXCEPTION and then running a compare using CHECK. Incorrect CHECK syntax is observed when the DELETE option is YES but no exception is used.
Problem conclusion
The problem has been resolved.
Temporary fix
Comments
APAR Information
APAR number
PM28712
Reported component name
DB2 OBJECT COMP
Reported component ID
5697G6400
Reported release
720
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-12-10
Closed date
2011-01-31
Last modified date
2011-03-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
ADB2USKO
Fix information
Fixed component name
DB2 ADMIN TOOL
Fixed component ID
568851500
Applicable component levels
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":"SSCVQTD","label":"IBM Db2 Administration Tool for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"720","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
02 March 2011