Using search tokens
Tokens are used to identify MainView Transaction Analyzer search terms in:
- URL shortcuts
- REXX EXECs
- BMC AMI Ops batch report requests
Consider the following information as you use these tokens:
- The token itself can be typed as all lowercase or all uppercase characters; either atp= or ATP= is valid.
- The value that follows a token is case-sensitive. The Type column in following table identifies the type of value that is valid
- Mixed indicates the token accepts mixed-case values and distinguishes between uppercase and lowercase letters. For example, you can specify either abcd or ABCD for a CICS transaction ID; however, a search for abcd will not find instances of ABCD. Some mixed-case values can also include special characters, as in a CICS terminal ID.
- Hex indicates the token requires the value to be spelled out in hexadecimal characters. For example, a WebSphere MQ message must be supplied in hexadecimal format because such messages often contain special characters that might otherwise be interpreted as instructions.
- List indicates the token accepts only values from a predefined list, such as Y or N for yes or no.
- Caps in the Type column means you must specify the value in all uppercase. For example, a Db2 authorization ID must always be specified in uppercase.
- BMC AMI Ops accepts up to 8 parameters of up to 256 characters each. You can string search terms together to make one longer parameter provided it does not exceed 256 characters in total.
Search term tokens
Token | Description | Format | Type |
|---|---|---|---|
atp | WebSphere application type Usage: List components | CICS | IMS | IMSB Note: IMS includes IMSB. Example: atp=CICS | list |
aut | Db2 authorization ID Usage: List components | 1-8 characters Example: aut=MTASTC | caps |
ccn | Db2 connection name Usage: List components | 1-8 characters Example: ccn=MTACS22D | caps |
cor | Correlation ID Usage: Correlation | 60 hexadecimal characters Example: cor=E4E2C2D4...D7000100000000 | hex |
cpf | CPU minimum Usage: List components | Seconds, with optional decimal point Example: cpf=0.0005 | caps |
cpt | CPU maximum Usage: List components | Seconds, with optional decimal point Example: cpt=1.2 | caps |
ctg | CTG application ID Usage: List components | 1-8 characters Example: ctg=MTACTG71 | caps |
ctp | Db2 connection type Usage: List components | BMP | CAF | CICS | CTL | DDF | DRDA | Example: ctp=DRDA | list |
dbs | Db2 subsystem ID Usage: List components | 1-8 characters Example: dbs=DH01 | caps |
dur | Duration Usage: List components | hh:mm:ss.tt Example: dur=01:30:00 | caps |
elf | Elapsed time minimum Usage: List components | Seconds, with optional decimal point Example: elf=0.5 | caps |
elt | Elapsed time maximum Usage: List components | Seconds, with optional decimal point Example: elt=1.75 | caps |
exc | Exclude CICS Usage: List components | Y Example: exc=Y | list |
exd | Exclude Db2 Usage: List components | Y Example: exd=Y | list |
exg | Exclude CTG Usage: List components | Y Example: exg=Y | list |
exi | Exclude IMS Usage: List components | Y Example: exi=Y | list |
fun | WebSphere MQ function Usage: List components | GET | PUT | PUT1 Note: PUT includes PUT1. Example: fun=PUT | list |
glf | WebSphere MQ latency minimum Usage: List components | hh:mm:ss.tt Example: glf=00:01:30 | caps |
glt | WebSphere MQ latency maximum Usage: List components | hh:mm:ss.tt Example: glt=00:05:00 | caps |
ini | Is component an originating UOW? Usage: Correlation | Y | N Example: ini=Y | list |
ius | IMS user ID Usage: List components | 1-8 characters Example: ius=MTASTC | caps |
lev | MQ correlation level Usage: Correlation | 0-9 Example: lev=9 | caps |
lst | Component types to list Usage: List components | C (CICS) Example: lst=Q | list |
max | Maximum to search Usage: List components | 1-999999 Example: max=1000 | caps |
mpt | Maximum transactions to correlate Usage: List components | 1-99 Example: mpt=10 | caps |
msg | Message ID Usage: Correlation | 48 hexadecimal characters Example: msg=C3E2D840D4E3...077D354C | hex |
ori | Originating UOW? Usage: List components | Y (originating only) Default is both originating and non Example: ori=Y | list |
per | Report period Usage: List components | M | MIN Example: per=HOUR | list |
pgm | CTG program Usage: List components | 1-8 characters Example: pgm=ECIPROG2 | caps |
pln | Db2 plan Usage: List components | 1-8 characters Example: pln=MTACOM1N | caps |
psb | IMS PSB Usage: List components | 1-8 characters Example: psb=DFHSAM05 | caps |
qmr | WebSphere MQ queue manager Usage: List components | 1-8 characters Example: qmr=MTA5 | caps |
qnma | WebSphere MQ queue name Usage: List components | 1-48 characters Example: qnm=MTA.Reply.Message | mixed |
reg | CICS region Usage: List components | 1-8 characters Example: reg=MTACEME5 | caps |
res | WebSphere MQ queue type Usage: List components | R (resolved) Example: res=R | list |
rgn | IMS region Usage: List components | 1-8 characters Example: rgn=MTMAIE22 | caps |
row | Maximum report rows Usage: List components | 1-999 Example: row=100 | caps |
rtp | CTG correlation type Usage: Correlation | 6 (TGID) Example: rtp=6 | list |
sco | Scope Usage: List components | A | ALL Example: sco=LOCAL | list |
ser | CTG server Usage: List components | 1-8 characters Example: ser=MTACS320 | caps |
spn | Time span Usage: Correlation | 32 hexadecimal characters Example: spn=C191987BBB68...BBBE9F708 | hex |
ter | CICS terminal Usage: List components | 1-4 characters Example: ter={AA1 | mixed |
timb | Time range Usage: Correlation, List components | YYYYMMDDhhmmssttYYYYMMDDhhmmsstt Example: | caps |
tpn | CTG transaction Usage: List components | 1-4 characters case Example: tpn=CSMI | mixed |
trn | CICS transaction Usage: List components | 1-8 characters Example: trn=ecit | mixed |
tsk | CICS task number Usage: List components | 1-99999 Example: tsk=56612 | caps |
txn | IMS transaction Usage: List components | 1-8 characters Example: txn=IMSMQGT | caps |
txt | CTG transaction type Usage: List components | EXM | SOR | XA | NONE | UN Example: txt=EXM | list |
typ | Component type to correlate Usage: Correlation | C | CICS Note: WebSphere MQ components use the Example: typ=C | list |
uid | CTG user ID Usage: List components | 1-8 characters Example: uid=mtastc | mixed |
usr | CICS user ID Usage: List components | 1-8 characters Example: usr=MTASTC | caps |
utc | Is date UTC/GMT? Usage: Correlation, List components | Y | N Default is N, which means the value Example: utc=Y | list |
wksc | Db2 workstation name Usage: List components | 1-18 characters Example: wks=WebSphere+Appl+Ser | mixed |
wkuc | Db2 workstation end user Usage: List components | 1-16 characters Example: wku=Weekly+Sales | mixed |
xid | First 70 bytes of the XA transaction ID (XID) Usage: Correlation | 140 hexadecimal characters Example: xid=C3E2D840D4E3...077D354C | hex |
xi2 | Last 70 bytes of the XA transaction ID (XID) Usage: Correlation | 140 hexadecimal characters Example: xi2=C191987BBB68...BBBE9F708 | hex |
xpt | Exceptions only Usage: List components | Y Example: xpt=Y | list |
a The qnm value can contain one or more asterisks. For example, a search for *.Prod.*.Reply finds both S1.Prod.Test.Reply and S2.Prod.Acctg.Reply. The queue names to be searched are locally named queues unless res=R is also specified, in which case resolved queue names are searched.
b The tim token is used in URLs and the NVBAPI instead of the separate early and late date and time fields that are used in search dialogs. tim can also be used for correlation requests, if the time span field is not available.
c The wks and wku tokens treat single-character wildcards (? and +) as matching blanks, as well as non blank characters. For example, a search for My+Workstation will find workstations named My Workstation.
Related topics