Notification detail's pattern matching is not working as expected between Windows and Unix systems
search cancel

Notification detail's pattern matching is not working as expected between Windows and Unix systems

book

Article ID: 415794

calendar_today

Updated On:

Products

CA Automic Applications Manager (AM)

Issue/Introduction

Applications Manager's notification detail has a number of options for attaching registered output files. One option is Pattern which allows for attaching files of a particular name. This field value uses regular expression (regex).

This pattern value is checked against all registered output files of a Job, and if the pattern value matches output filename value, the output is attached.

In Unix/Linux OS masters, the pattern value matching behavior is as follows:

  • If the pattern value contains the file separator forward slash ( / ), the pattern value is checked against all registered output files where the output filename INCLUDES the full path (e.g. /appworx/out/output.txt).
  • If the pattern value does not contain the file separator forward slash ( / ), the pattern value is checked against all registered output files where the output filename DOES NOT INCLUDE the full path (e.g. output.txt)

In Windows OS masters, the pattern value matching behavior ONLY works as follows:

  • Whether or not the pattern value contains a forward slash ( / ), the pattern value is ALWAYS check against all registered output files where the output file name DOES NOT INCLUDE the full path (e.g. output.txt)


This difference in behavior may become an issue when migrating masters from Unix/Linux to Windows or vice versa.

Note that pattern matching in Output Scans is not affected and works the same way in both Unix/Linux and Windows, which is determined if a file separator is found or not found.

Cause

defect in pattern matching code. 

Resolution

Workaround:

For Windows, keep in mind that that pattern matching is checked only against the file name that does not include the full path.

Solution:

A fix will be included in Applications Manager version 9.6.2