FILDMGRM (file damaged)

Purpose
The file may be damaged. Some of the indications of a damaged file in the local VSAM file system are:
  • The file-change date and time recorded by a VSAM API is not the same as the file-change date and time recorded by the file system. The function continues processing (SVRCOD=4).

    Either an aborted DDM application has left the file in an inconsistent state or a non-DDM application has changed the file. The local VSAM file system resynchronizes the file-change date and time if it can get write access to the file, unless a higher severity condition prevents it from doing so. Re-synchronizing the date and time corrects only this particular file-damaged condition, but the file may still be damaged. To verify that the file is not damaged, use DDMCopyFile or DDMUnLoadFileFirst with AccessFlags=DDM_BYPDMG|DDM_RTNINA and inspect the result.

  • An index file is not consistent with its base file. The function is rejected (SVRCOD=16).

    The file-change date and time recorded by the VSAM API for the base file is not the same as the base file's file-change date and time that was recorded as an attribute of the index file. Either an aborted DDM application has left the file in an inconsistent state or a non-DDM application has replaced a base file or an index file without replacing all of the files in the file object. The local VSAM file system does not resynchronize the file-change date and time.

Both of the above conditions can exist at the same time for the same index file, causing two FILDMGRM reply messages to be returned, one for SVRCOD=4 followed by one for SVRCOD=16.

Code Point
The code point for this term is X'125A'.
Structure
See Reply message structure for the general structure of reply message data.
Parameter
Description
SVRCOD
Severity code
  • Code point is X'1149'.
  • Returned.
  • Enumerated value(s) for this parameter:
    4
    Warning Severity Code
    8
    Error Severity Code
    16
    Severe Error Severity Code
    32
    Access Damage Severity Code
    64
    Permanent Damage Severity Code
FILNAM
File name
  • Code point is X'110E'.
  • Returned.
CSRPOSST
Cursor position status
  • Code point is X'115B'.
  • Returned.
DTALCKST
Data lock status
  • Code point is X'115C'.
  • Returned.
RECCNT
Record count
  • Code point is X'111A'.
  • Minimum value is 0.
RECNBR
Record number
  • Code point is X'111D'.
  • This is the record number of the record being operated on by the function.
SRVDGN
Server diagnostic information
  • Code point is X'1153'.
  • No information is returned.
  • Enumerated value for this parameter:
    1
    Either an aborted DDM application has left the file in an inconsistent state or a non-DDM application has changed the file.