A fix is available
APAR status
Closed as program error.
Error description
REORG MAPPING DB field in DSNTIP62 has only 7 bytes for input, but the corresponding parm REORG_MAPPING_DATABASE could accept a character string of maximum 8 bytes. . DB2 UTILITIES PARAMETERS PANEL 3 ===> Enter system-level backup options for RESTORE SYSTEM and RECOVER below: 1 SYSTEM-LEVEL BACKUPS ===> As a recovery base: NO or YES 2 RESTORE/RECOVER ===> From dump: NO or YES 3 DUMP CLASS NAME ===> For RESTORE/RECOVER from dump 4 MAXIMUM TAPE UNITS ===> For RESTORE SYSTEM: NOLIMIT or 1-255 Enter other DB2 Utilities options below: 5 REORG PART SORT NPSI ===> 1234567 AUTO/NO/YES online REORG NPSI sort 6 REORG LIST PROCESSING ===> 12345678 PARALLEL/SERIAL REORG list processing 7 REORG MAPPING DB ===> 1234567 Default database for mapping table for REORG TABLESPACE SHRLEVEL CHANGE
Local fix
N.A.
Problem summary
**************************************************************** * USERS AFFECTED: All users of the DB2 11 for z/OS * * installation CLIST are affected by this * * change. * **************************************************************** * PROBLEM DESCRIPTION: A DB2 for z/OS database name can be up * * to 8 bytes long but the REORG MAPPING * * DB field on installation panel DSNTIP62 * * currently accepts a maximum of 7 bytes. * **************************************************************** * RECOMMENDATION: * **************************************************************** The DB2 subsystem parameter DSN6SPRM.REORG_MAPPING_DATABASE allows you to specify the name of a database that the REORG utility uses to implicitly create the mapping table when the control statement for a REORG TABLESPACE with SHRLEVEL CHANGE request does not include the MAPPINGTABLE keyword. When you run the DB2 installation CLIST, you can set the DSN6SPRM.REORG_MAPPING_DATABASE parameter by means of the REORG MAPPING DB field on installation panel DSNTIP62. Currently, a bug in panel DSNTIP62 causes it to restrict the maximum length of entries in the REORG MAPPING DB field to 7 bytes instead of 8.
Problem conclusion
In response, this APAR corrects DSNTIP62 to permit an entry of up to 8 bytes in the REORG MAPPING DB field.
Temporary fix
Comments
APAR Information
APAR number
PI16182
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
B10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-04-16
Closed date
2014-07-01
Last modified date
2014-08-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI19289
Modules/Macros
DSNTIP62
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RB10 PSY UI19289
UP14/07/16 P F407
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":"11.0","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":"11.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
04 August 2014