You are here: LANSA for i User Guide > 5. Housekeeping > 5.14 Impact Analysis > 5 14 4 Impact List Profile Search

5.14.4 Impact List - Profile Search

When the Add/Create function key is used on the 'Work with List Entries' screen a Profile Search is initiated. A Profile Search looks for objects with particular attributes. The objects found are added to the entries in the list. The search may be run in batch or interactively. If run interactively the list is redisplayed with the added entries highlighted.

To perform a Profile Search you must:

1.  Select the type of object to be searched for.

2.  Enter the characteristics to be searched for and the Run in Batch option.

Step 1: Select the type of object to be searched for

The type of object to be searched for is selected from the box presented when the Add/Create function key is used.

 

                 ........................................

                 :     Add Entry by Profile Search      :

                 :  Use cursor to make a selection      :

                 :   Add Fields                         :

                 :   Add Files                          :

                 :   Add Functions                      :

                 :   Add System Variables               :

                 :   Add Multilingual Variables         :

                 :   Add Changed Objects                :

                 :   Cancel Add Request                 :

                 : Fnn=Help Fnn=Cancel Fnn=Messages     :

                 :......................................:

 

 

Step 2: Enter the characteristics to be searched for

The characteristics to be searched for and the Run in Batch option are entered on a screen of possible attributes. This screen is presented after the selection of the type of object and will vary according to the type selected.

For example:

Field Type

EQ

A

Length

EQ

6

Default value

EQ

*YYMMDDC

Only fields which are alpha with a length of 6 and a default value of *YYMMDDC will match and be added to the list.

It is possible to enter a list of values for some attributes. That attribute is considered matched if it is any of the values in the list.

For example:

Field Type

EQ

A

Length

EQ

6

Default value

LS

*YYMMDDC *DDMMYYC

The fields which match and are added to the list will be alpha with a length of 6 and have a default value. That default value will be *YYMMDDC or *DDMMYYC.

It is possible to search on the Last Action Details date and action.

For example:

File Name

EQ

EMP

Last Action

LT

19970518 CM  (YYYYMMDD Action)

The files which match and are added to the list will start with 'EMP' and were last compiled before 18th May 1997.

If no Action is specified in the Last Action Details search all actions are applicable

For example:

File Name

EQ

EMP

Last Action

GT

19970430 __  (YYYYMMDD Action)

The files which match and are added to the list will start with 'EMP' and were last actioned in some way after 30th April 1997.

Operations

 

EQ

equal to

=

equal to

NE

not equal to

GE

greater than or equal to

>=

greater than or equal to

GT

greater than

>

greater than

LE

less than or equal to

<=

less than or equal to

LT

less than

<

less than

IN

Contains

LS

List

LK

Like (SQL pattern)

Not all Operations are valid for some attributes. See individual attributes for valid Operations. The testing for an IN (contains) operation is not case sensitive. The testing for EQ, = and NE operations is case sensitive. The value specified with an IN (contains) operation should be left aligned. Do not enclose values in quotes unless quotes are part of the value.  Where multiple values can be specified for an attribute but an EQ, = or NE operation is used, the value should be entered in the first value position. Values for Description and Help Text plus Label and Column Heading for fields are assumed to be in the language currently being used in the partition and only the current language contents of these attributes are searched.

The LK (Like) operation uses the full value field in an SQL WHERE command. This means trailing blanks are significant. If you do not wish to match trailing blanks, you must fill the value with % (e.g., Field name LK %MONTH%%%%).

Examples of LK operation: