3.2.7.4 File Screen Events

  • Article

If an I/O operation happens on a path that is within the scope of a File Screen.Folder path of a File Screen (section 3.2.1.3.1), the File Server Resource Manager Protocol MUST check to see if the file name of the I/O is blocked by the File Screen (section 3.2.1.3.1).

A File Screen Event MUST occur if the following criteria are met:

  • The file name is part of at least one of the blocked file groups.

  • The file name is not part of any of the allowed file groups of any file screen exceptions configured on that path.

A file name is part of a file group if, and only if, the following criteria are met:

  • The file name matches at least one of the file name patterns in the members of the file group.

  • The file name does not match any of the file name patterns in the non-members of the file group.

All comparisons of the file name with any of the patterns specified above MUST be case-insensitive.

Section 3.2.4.1 specifies how the File Server Resource Manager Protocol responds to File Screen Events.

If FileScreen notifications are setup when a File Screen Event occurs, the server will resolve file screen macros from section 3.2.4.3.2 and general macros from section 3.2.4.3.4 that are specified in the notification email messages, event messages and/or action arguments. Any other macros will be left unresolved.

If the Enable file screen audit parameter is true, the server MUST keep records of the file screen events that can be used by FSRM when generating a file screen audit report. If the Enable file screen audit parameter is false, the server does not keep records of file screen events.