Using '?' Wildcards in conditions gives an AwE-9999 (Dangling meta character) error.
search cancel

Using '?' Wildcards in conditions gives an AwE-9999 (Dangling meta character) error.

book

Article ID: 88890

calendar_today

Updated On:

Products

CA Automic Applications Manager (AM)

Issue/Introduction

Using '?' Wildcards in conditions gives an AwE-9999 (Dangling meta character) error.

Environment

Release: AAMOS499000-8.0-Automic Applications Manager-OS400 Agent
Component:

Resolution

Applicable toApplications Manager Versions:  v7.x, v8.0

 

Symptoms

?Using wildcard(s) in a check file condition to specify 'x' number of wildcards was done as following in v5.1 of AM.

     Before check file

     if testfile???.txt exists

     then

     run task

Such a condition would be satisfied by a filename of testfile123.txt or testfile456.txt but fail for testfile12.txt or testfile1234.txt. However, running a similar condition in v7.1 or 8.0 gives the following error:

APLX80:ErrorMsg: AwE-9999 Internal error (6/13/12 2:58 PM)
Details: Dangling meta character '?' near index 10
testfile??????.txt
          ^
null


Solution

?Since v7.1 of AM the backend is now Java based as opposed to 'c' which v5.1 (and v6.1) was written in. The way the Application is written the use of '?' is now replaced with the '.' character.

For the above example, using a testfile....txt (3 wildcard '.' and 1 for the extension itself) with a total of 4 '.' wildcards works correctly.