Midrange News for the IBM i Community


Posted by: renojim
IBM error message interpretation
has no ratings.
Published: 06 Nov 2016
Revised: 14 Nov 2016 - 194 days ago
Last viewed on: 27 May 2017 (403 views) 

Using IBM i? Need to create Excel, CSV, HTML, JSON, PDF, SPOOL reports? Learn more about the fastest and least expensive tool for the job: SQL iQuery.

IBM error message interpretation Published by: renojim on 06 Nov 2016 view comments(2)

Friday afternoon I had a production issue, which turned out to be data, but I had this message in the job log, and I simply do not understand what the H it means. Doing my best to reduce it to plain english, it translates to something like 'you can't copy a file to qtemp because the file format for the the file is in a different ASP than the file'... or something like that. This one's over my head, but for educational purposes if somebody knows what it means, I sure would appreciate you passing it along:

From module . . . . . . . . :   QDBCRTFI                                      
From procedure  . . . . . . :   SEND_PMSG                                     
Statement . . . . . . . . . :   42774                                         
Message . . . . :   A new format was created for file MF1234W in QTEMP.       
Cause . . . . . :   File MF1234W in library QTEMP was requested to use format
  MF1234WR from file *N in library *N on ASP 33. However, format MF1234WR from
  file *N is not available to be used for reason code 2.  The reason codes are
  as follows: 1 - The based on file *N for logical file MF1234W is a          
  Structured Query Language (SQL) table containing a field(s) that does not   
  have a default value(s). A new format MF1234WR for logical file MF1234W was
  created from format MF1234WR of file *N because the attributes of the format
  required modification. 2 - The Auxiliary Storage Pool (ASP) 1 for file      
  MF1234W in library QTEMP is not the same as ASP 33, which is the ASP of the
  file owning the format. A new format MF1234WR for file MF1234W was created  
  from format MF1234WR because database files cannot share formats with       
  database files on a different ASP. 3 - The format contained attributes which
  were not correct. Therefore, the format level identifier was changed to     
  match the correct attributes of the corrected format. 4 - The format was      
  shared and the CCSID value was changed, or multiple logical files shared      
  this format, and their based on physical files were different. 5 - The        
  format was shared by files that were not dependents of file MF1234W. A        
  change to a file format will only affect that file and any dependents of      
  that file that share its format. 6 - Either the based on file for logical     
  file MF1234W in library QTEMP, or the file *N in library *N has an identity   
  column and/or a row change timestamp which are SQL generated columns.  A new  
  format MF1234WR for logical file MF1234W was created from format MF1234WR of  
  file *N because the generated column(s) required modification(s).            

Return to midrangenews.com home page.
Sort Ascend | Descend

COMMENTS

(Sign in to Post a Comment)
Posted by: DaleB
Premium member *
Reading, PA
Comment on: IBM error message interpretation
Posted: 6 months 16 days 11 hours 24 minutes ago

How is the file created? CPYF CRTFILE(*YES), CRTDUPOBJ, CRTPF with a FORMAT(xxx) in the source, ...?

Posted by: renojim
Premium member *
Comment on: IBM error message interpretation
Posted: 6 months 13 days 5 hours 54 minutes ago

It was CRTDUPOBJ, which is not the standard way of doing things around here.