PK34729: WHEN BP SET FOR VERY SMALL SPACE OBJECT COMPARE DOES NOT PUT UNLOAD DATA TO TAPE WSL RUNS S837 U4094

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• User sets up their BP to be very small:
  Space parameters:
       Unit name         ===> SYSDA
       Space unit  . . . ===> TRK
       Max Primary . . . ===> 1
       Max DASD  . . . . ===> 1
       Tape Unit . . . . ===> TAPE
  Then uses Object Compare on a table with millions of rows. The
  unload statement for the data should have gone to TAPE but did
  not. Statement still shows:
  -STA DB(DB89308X) SPACE(TS89308X) ACCESS(RO);
  TSODELETE 'XXXXX.B@89308.B@89308.CNT.T0001';
  TSODELETE 'XXXXX.B@89308.B@89308.ULD.T0001';
  TEMPLATE UTLPUNCH DSN 'XXXXX.B@89308.B@89308.CNT.T0001'
           UNIT SYSDA;
  TEMPLATE UTLREC DSN 'XXXXX.B@89308.B@89308.ULD.T0001'
           UNIT SYSDA;
  UNLOAD DATA FROM TABLE
  "XXXXX"."T89308"
  If WSL is run it fails with:
  IEC028I 837-08,IFG055
  u4094 s837 rc08 rc=4094 4094
  

Local fix

• Please apply PTF when available.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Object Comparison Tool, who use *
  *                 sizable Table and only allocation small DASD *
  *                 space, may be affected.                      *
  *                 .* Note: ie. Requesting unload to tape in    *
  *                 APPLY processing did not get accepted.       *
  ****************************************************************
  * PROBLEM DESCRIPTION: When  BP  were set  up to be very small *
  *                      Space parameters and the Object Compare *
  *                      was  used  on  a table with millions of *
  *                      rows, the unload statement for the data *
  *                      should  have gone to  TAPE but did not. *
  *                      If  WSL  was run it failed with IEC028I *
  *                      837-08,IFG055 U4094 S837 RC08.          *
  *                      .*                                      *
  *                      Max DASD  was set to be small to enable *
  *                      use  of  tape for APPLY job output data *
  *                      sets.  Panel  ADB2UPA  also used a very *
  *                      small primary DASD  allocation. However *
  *                      Object  Compare  outputs  went  to DASD *
  *                      instead of tape.  Space  problems would *
  *                      then follow.                            *
  *                      .* Note:                                *
  *                      Exec GOCGAJOB has been modified to use  *
  *                      tape for the output datasets  for  the  *
  *                      circumstance described.                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  See Problem Description.
  

Problem conclusion

• Apply the fix.
  

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:

Modules/Macros

•    GOCGAJOB
  

Fix information

• Fixed component name

  DB2 OBJECT COMP

• Fixed component ID

  5697G6400

Applicable component levels

• R710 PSY UK20898

     UP06/12/30 P F612

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.