mark landin ([log in to unmask]) wrote:
: In article <[log in to unmask]>,
: [log in to unmask] says...
: >
: >I have a KSAM(classic type 2 files) file which generates the following
: >errors.
: >
: >1.  Using LISTF:
: >       Bad UFID for the file/<my file> (CIWARN 9165)
: >       END OF FILE  (FSERR 0)
: >       File system error 0 encountered on list file.(CIERR 425)
: >
: >2.  Using STORE:
: >       /<my file> NOT STORED: LABEL MANAGEMENT ENCOUNTERED ERROR
: >                                     ACCESSING FILE LABEL
: >I tryed storing the account and then doing a PURGEACCT but got the "Bad
: >UFID error"  I found a program in .PUB.SYS called BDLABEL.  But it wants a
: >version #.  I would appreciate any information that would help me resolve
: >this problem.
 
: This is an indication of file system corruption. I had the same problem
: last month. I strongly recommend you call the Response Center.
 
You are correct that a bad UFID is an indication of file system corruption.
I thought I might provide a small discussion on what a UFID is and how a
bad UFID is discovered.
 
UFID stands for Unique File IDentifier, and the structure that informs MPE
where the file label on disk is located.  The UFID is composed of the
Volume ID, the label table offset, and a time stamp.  The Volume ID tells
MPE which label table to use.  The label table offset is the offset of the
file label in the specific label table.  The time stamp is used for
verification.
 
Since the label table offsets can be used over and over from file creations
and deletions, the time stamp is used to verify that the file label that
is being pointed to by the UFID is file in the file label.  The file label
keeps the same time stamps that are in the UFID.  If they don't match, you
have a bad UFID.  Bad UFIDs can also be generated by the extent descriptors
pointing back to the incorrect file label.  These checks are done at open time.
 
I realize that bad UFIDs are inconveinent, but these checks stop
further corruption and make it harder for people to generate UFIDs and
attempt to open files directly.  By the way the file label creation time
stamps and the UFID time stamps are not the same.
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Rick Ehrhart
[log in to unmask]