create view LIB.ViewName
(...fields)        
as
select ...fiedls
from tables

union all

SELECT ...fields
from tables

[SQL0901] SQL system error. Cause . . . . . :   An SQL system error has 
occurred.  The current SQL statement cannot be completed successfully.  The 
error will not prevent other SQL statements from being processed. Previous 
messages may indicate that there is a problem with the SQL statement and SQL did 
not correctly diagnose the error. The previous message identifier was MCH1210. 
Internal error type  3107  has occurred. If precompiling, processing will not continue 
beyond this statement. Recovery  . . . :   See the previous messages to determine 
if there is a problem with the SQL statement. To view the messages, use the 
DSPJOBLOG command if running interactively, or the WRKJOB command to view the 
output of a precompile.  An application program receiving this return code may 
attempt further SQL statements.  Correct any errors and try the request again.

MCH1210 Receiver value too small to hold result

When running a backup, I am getting error code MCH1210 received by 
SAVLIBZ even though I already have PTF  508  installed. 

We found an obscure sequence of events that could still cause a variable to 
overflow. A fix for this has been developed which corrects the problem. The fix is 
now available as a PTF. This PTF can only be installed on a Release  5 . 09  version of 
DSK Manager. The correction is available in PTF package DMPTF510. E-mail us and 
request the PTF package to correct this problem. 

APAR Error Description / Circumvention 

DESCRIPTION OF PROBLEM FIXED FOR APAR MA28012 :
 -----------------------------------------------
 
  This MCH1210 exception is the result of corrupted response
  time bucket data within the QAPMCONF performance database
  file.  This data has been corrupted in all QAPMCONF files
  since V5R2M0 was installed, but the corruption is not always
  detected by the reporting tools.

  In addition, stopping and restarting data collection for a
  Collection Services category within the same Management
  Collection Object will cause a loss of data for that category.
  This can happen when a *CUSTOM collection profile is used to
  change the data collected, or when Management Central Monitors
  are stopped and restarted without a system profile collection
  active.  This can result in any of the following:
  ( 1 ) Data collected before the category was stopped will be
  missing from the performance database files created from the
  Management Collection Object by CRTPFRDTA.
  ( 2 ) An MCH1210 exception may occur in any tool using the
  affected performance database files.
  ( 3 ) Unpredictable results may occur if CRTPFRDTA processes
  the same Management Collection Object while the category is
  being restarted.

create view LIB.ViewName
(...fields)        
as
select *
from 
  (select ...fiedls
  from tables
  union all
  select ...fields
  from tables)