× 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.



On Thu, 2005-05-19 at 19:41 -0400, Chaudhary, Sachin (GE Equipment
Services, Consultant) wrote:
> 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)

The 'format level id' to which you refer is a checksum that's computed
on the _structure_ of a record, not it's content.  

The format level identifier is computed on the field names, field
lengths, types, and decimal positions.  If you add a field, change a
field name, field type, or field length, the iSeries will compute a
different format level id when the file is compiled.

When an RPG program is compiled, the default action of the compiler is
to record the format level identifiers of all files used in the program,
and upon opening each file, the program compares the compiled in
identifier with that of the file that was opened.  If they are
different, an error is signaled to indicate you are trying to run the
program over an incorrect version of the file.

You can compile a file over and over and it will have the same format
level identifier, until you change the DDS.

> 
> 
> 2. How can we know from which AS400 id was this object deleted?. History log 
> (DSPLOG QHST) is no good.

I believe you have to turn on object auditing, check the archives.


--
Regards,
Rich

Current Conditions in Des Moines, IA
Clear
Temp 69.8F
Winds out of the North at 9mph



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.