× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Sachin,

Correct, you wasted 2 hours.

The format level ID only changes if the file has fields removed/added, the size 
or type or the field changes or the field or record gets a new name.

If you do a DSPFD, the format level ID to check is listed as:
Record Format List                            
                       Record  Format Level   
 Format       Fields   Length  Identifier     
 HRIOH            28      196  3A5199514FDA0  

Note that as long as Format Level Identifier is the same, you will not get a 
level check.

However, the File Level identifier and Member level identifier will change 
anytime the file/member is created.  The DSPFD output is as follows:
Data Base File Attributes                                                
  Externally described file . . . . . . . . . :            Yes           
  File level identifier . . . . . . . . . . . :            1021103080502 
Member Description                                                       
  Member  . . . . . . . . . . . . . . . . . . : MBR        HPIOH         
    Member level identifier . . . . . . . . . :            1021103080502 

Having one or both of these IDs change will not cause a level check.


You can for instance, change the TEXT or COLHDG of a file and recreate it 
without problems.


HTH,

Charles Wilt
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Chaudhary, 
> Sachin (GE
> Equipment Services,Consultant)
> Sent: Thursday, May 19, 2005 7:41 PM
> To: RPG programming on the AS400 / iSeries
> Subject: File object got deleted!
> Importance: High
> 
> 
> Hi
> 
> Today somebody deleted a PF from production, which holds the 
> key to Invoice number, which stalled majority of Billing 
> applications for 2 hours right in the Morning!!
> I have 2 questions related to this:
> 1. Thinking that creating a new file from DDS will lead to 
> recompiling all programs to avoid level check error, as a 
> norm we can't compile with level check *NO) I requested the 
> backup restore for which the AS400 operator took around 
> 1hr45min. I wanted to restore the object in Production 
> library so Format Level Identifier does not change, but he 
> put it in my QPGMR libr. Creating a duplicate object, to 
> production didn't change the Identifier??
> I created the same object from DDS, the ID didn't change 
> either...I wasted 2 hours just like that?? (I already knew 
> what data should be in the file.)
> Can you explain me? Unless I change structure of file the 
> format level id which has a reference in program object never 
> gets changed? i.e. checking in the objects using implementer 
> is good (lets forget the old data in the file for sometime)
> 
> 
> 2. How can we know from which AS400 id was this object 
> deleted?. History log (DSPLOG QHST) is no good.
> 
> Thanks
> Sachin
> 
> -- 
> This is the RPG programming on the AS400 / iSeries (RPG400-L) 
> mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
> 
> 


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.