![]() Matches every file except those that end in ".tmp" (case insensitive). Matches every file except those named "." or ".". Matches every file except a file that ends in ".edi" (case insensitive). Matches every file except a file that ends in ".edi" (case sensitive). ![]() Matches every file except a file called "TestFile" (case insensitive). Matches every file except a file called "TestFile" (case sensitive). Matches test0.edi through test9.edi, test00 through test99.edi, etc. Matches testaaa0.edi through testccc9.edi (lower or upper case) Matches test.edi through test (any character(s)). The table below contains some examples that might be used for file name searches. Literal string should be closed with \E.Įnds an escaped (quoted) literal string that was started by \Q. Starts an escaped (quoted) literal string. Necessary if you want to match to a period ('.'), bracket (''), brace ('') or other special character. Indicates the preceding characters must appear at the end of the stringĮscapes (quotes) the following character. Indicates the subsequent characters must appear at the beginning of the string Table 3. POSIX Character Classes Construct Table 2. Predefined Character Classes Construct For a more complete list of regular expression constructs and a more detailed discussion, visit. This section provides descriptions of some commonly used constructs within regular expressions. Invalid - contains two regex patterns within one token (i.e., the filename token) Invalid - does not consume the entire filename token Below is a table containing some valid and invalid regular expression examples. Furthermore, the pattern must consume the entire token. Only one regex pattern is allowed per token, for example, a filename or a directory token.Note that, as seen in this example, it is possible for a regular expression to contain brackets as part of the pattern definition itself however, it is still necessary to enclose the complete pattern in its own pair of brackets. The regex pattern must be enclosed in brackets (for example, \.edi] or ).Regular expressions (abbreviated regex) are composed of a special syntax that enables a wider range of search patterns. All regular expression usage must follow these basic rules. When the basic wildcards do not provide the needed search criteria, regular expressions may be used instead. For example, " PUT ab*.*" and " PUT ab?.*" are both acceptable. Note that, when using wildcards, it is possible to use multiple wildcards within the same token. The following commands produce the following results. For example, assume the outbox has the following files. Wildcards are represented by * or ?, where * matches multiple characters and ? matches only a single character. Searches first for directories that end in box (for example, inbox or outbox), and next for the subdirectories that match the regular expression a.* , and finally for files that match the regular expression ab.*\.edi Searches first for directories that end in box (for example, inbox or outbox) and next for files that match the regular expression ab.*\.edi Searches myOutbox for all files that match the regular expression ab.*\.edi Searches myOutbox for all files that match the pattern ab?edi Searches myOutbox for all files that match the pattern ab*.edi As an introduction, the table below provides some examples. Refer to your specific command reference for locations where you can use wildcards and regular expressions. Some cases, however, allow for placement within the directory tokens, as well. Generally, wildcards and regular expressions are restricted to use only within the filename token of a path. The CHECK is only available with the Cleo Harmony and Cleo VLTrader applications. Wildcards and regular expression are most often used in the paths of GET, PUT, LCOPY, LDELETE, LREPLACE, and CHECK commands. This section describes the usage of wildcards and regular expressions.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |