...
The Find String in PUI DDS Source (PUIFNDSTR) command lets you search for character strings in the Profound UI metadata stored in DDS source code. You can use it to determine which widgets contain a given string or are bound to a particular DDS field.
...
Parameters
Keyword | Description | Choices | Notes | |||
|---|---|---|---|---|---|---|
STRING | Find 'string' | Character value, *ALL | Required | |||
PROPERTY | Property to search | Character value, *ALL | Required | |||
| SUBPROP | Sub-property to search | Character value, *NONE, *ALL | Optional | |||
SRCFILE | Source file | Qualified object name | Optional | |||
| Qualifier 1: Source file | Name, QDDSSRC |
|
| ||
Qualifier 2: Library | Name, *LIBL, *CURLIB | |||||
SRCMBR | Source member | Name, *ALL | Optional | |||
BNDONLY | Bound field names only | *YES, *NO | Optional | |||
MATCHCASE | Search is case-sensitive | *YES, *NO | Optional | |||
OUTPUT | Output | *, *OUTFILE | Optional | |||
OUTFILE | File to receive output | Qualified object name | Optional | |||
| Qualifier 1: File to receive output | Name | ||||
| Qualifier 2: Library | Name, *LIBL, *CURLIB | ||||
OUTMBR | Output member options: | Element list | Optional | |||
Element 1: Member to receive output | Name, *FIRST |
|
| |||
Element 2: Replace or add records | *REPLACE, *ADD |
|
Find 'string' (STRING)
Specifies the string you want to search for.
...
When the bound only (BNDONLY) parameter specifies *YES, only bound variables that exactly match this string will be returned.
Property to search (PROPERTY)
Specifies widget property name that will be searched.
...
Only widget properties that contain the specified string will be searched. For example, if you specify 'border' for this string, all widget property names that contain the word 'border' will be searched.
Sub-property to search (SUBPROP) 1
Specifies widget sub-property name that will be searched. Some widget properties (such as "value") contain sub-properties such as "zeroBalance" (as shown on the Binding dialog) or "translations" (as shown on the "Translation Settings" dialog). The sub-property name as stored in the JSON metadata may be slightly different than what is shown on the dialogs. For example, "Show Zero Balance" on the Binding dialog is stored in the metadata as "zeroBalance". To view the actual sub-property names, you can perform the following steps in the Profound UI Visual Designer:
...
Example: Command "PUIFNDSTR STRING(12345) PROPERTY(*ALL) SUBPROP(translations)" will find all instances where the sub-property "translations" contains string "12345", regardless of what property the sub-property "translations" belongs to. Command "PUIFNDSTR TRINGSTRING(12345) PROPERTY("column headings") SUBPROP(translations)" will find all instances where the sub-property "translations" of property "column headings" contains string "12345".
...
Only widget sub-properties that contain the specified string will be searched. For example, if you specify 'translations' for this tringstring, all widget sub-property names that contain the word 'translations' will be searched.
...
1(available in Profound UI Version 6, Fix Pack 7.0)
Source file (SRCFILE)
Specifies the file that contains the members that you want to search. This file should be a source physical file that contains DDS source code.
...
Specify the name of a library that contains the source file to be searched.
Source member (SRCMBR)
Specifies the name of the member to be searched.
...
Specify the name of a member in the source physical file to search.
Bound field names only (BNDONLY)
Specifies whether to limit the search to bound field names. Bound field names are DDS fields that have been connected to widgets in your display file.
...
Search for strings in both bound and un-bound properties. Any property that contains the STRING parameter (either an exact match, or when STRING is a substring of the widget property) will be returned.
Search is case-sensitive (MATCHCASE)
Specifies whether the search is case-sensitive.
...
The search will match any string found, regardless of upper/lower case letters. This is the default.
Output (OUTPUT)
Specifies where the output from the command is sent.
...
The output from the command is directed to the database file specified for the File to receive output (OUTFILE) parameter.
File to receive output (OUTFILE)
Specifies the database file that search output will be directed to if *OUTFILE is specified in the OUTPUT parameter. The format of this file must patch that of the FNDSTRP physical file provided with the Profound UI product.
...
Specify the name of a database file to receive the output. If this file does not exist, the PUIFNDSTR utility will create it.
Output member options: (OUTMBR)
Specifies the member in which search output will be placed.
...
If the member exists, new records returned by the current search will be added to the end of the member.
...
Examples for PUIFNDSTR
Example 1: Simple Command Example
| Code Block |
|---|
PUIFNDSTR STRING('js:') PROPERTY(*ALL) SRCFILE(SOURCE/QDDSSRC)
|
...
Example 2: Searching for a bound field
| Code Block |
|---|
PUIFNDSTR STRING(CUSTNO) PROPERTY(*ALL) BNDONLY(*YES)
|
This command will search all properties of all widgets and return all properties that have been bound to the CUSTNO field.
...
Error messages for PUIFNDSTR
*ESCAPE Messages | |
|---|---|
CPF9801 | Object &2 in library &3 not found. |
CPF9802 | Not authorized to object &2 in &3. |
CPF9810 | Library &1 not found. |
CPF9812 | File &1 in library &2 not found. |
CPF9820 | Not authorized to use library &1. |
PUI0041 | &1 errors detected during search. |
...