@broadcom/mat-analyze-for-zowe-cli 2.0.8 → 2.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (230) hide show
  1. package/LICENSE +17 -20
  2. package/README.md +1514 -1494
  3. package/lib/api/MATRest.js +16 -18
  4. package/lib/api/MATRest.js.map +1 -1
  5. package/lib/api/error/HistogramError.js +16 -18
  6. package/lib/api/error/HistogramError.js.map +1 -1
  7. package/lib/api/error/HttpError.js +1 -0
  8. package/lib/api/error/HttpError.js.map +1 -1
  9. package/lib/api/request/ICreateProfile.js +16 -18
  10. package/lib/api/request/ICreateProfile.js.map +1 -1
  11. package/lib/api/request/ICreateProfileRequest.js +16 -18
  12. package/lib/api/request/ICreateProfileRequest.js.map +1 -1
  13. package/lib/api/request/IInvokeProfile.js +16 -18
  14. package/lib/api/request/IInvokeProfile.js.map +1 -1
  15. package/lib/api/request/IInvokeProfileRequest.js +16 -18
  16. package/lib/api/request/IInvokeProfileRequest.js.map +1 -1
  17. package/lib/api/response/IAnalysis.js +16 -18
  18. package/lib/api/response/IAnalysis.js.map +1 -1
  19. package/lib/api/response/IAuth.js +16 -18
  20. package/lib/api/response/IAuth.js.map +1 -1
  21. package/lib/api/response/ICallStack.js +16 -18
  22. package/lib/api/response/ICallStack.js.map +1 -1
  23. package/lib/api/response/ICallerid.js +16 -18
  24. package/lib/api/response/ICallerid.js.map +1 -1
  25. package/lib/api/response/ICicstat.js +16 -18
  26. package/lib/api/response/ICicstat.js.map +1 -1
  27. package/lib/api/response/ICodeview.js +16 -18
  28. package/lib/api/response/ICodeview.js.map +1 -1
  29. package/lib/api/response/ICsect.js +16 -18
  30. package/lib/api/response/ICsect.js.map +1 -1
  31. package/lib/api/response/IDB2View.js +16 -18
  32. package/lib/api/response/IDB2View.js.map +1 -1
  33. package/lib/api/response/IDML.js +16 -18
  34. package/lib/api/response/IDML.js.map +1 -1
  35. package/lib/api/response/IDelayLocations.js +16 -18
  36. package/lib/api/response/IDelayLocations.js.map +1 -1
  37. package/lib/api/response/IDelayviews.js +16 -18
  38. package/lib/api/response/IDelayviews.js.map +1 -1
  39. package/lib/api/response/IHistogram.js +16 -18
  40. package/lib/api/response/IHistogram.js.map +1 -1
  41. package/lib/api/response/IHistory.js +16 -18
  42. package/lib/api/response/IHistory.js.map +1 -1
  43. package/lib/api/response/IIDMSModule.js +16 -18
  44. package/lib/api/response/IIDMSModule.js.map +1 -1
  45. package/lib/api/response/IIDMSModuleDetail.js +16 -18
  46. package/lib/api/response/IIDMSModuleDetail.js.map +1 -1
  47. package/lib/api/response/IIDMSTask.js +16 -18
  48. package/lib/api/response/IIDMSTask.js.map +1 -1
  49. package/lib/api/response/IIMSSSAView.js +16 -18
  50. package/lib/api/response/IIMSSSAView.js.map +1 -1
  51. package/lib/api/response/IIMSStatement.js +16 -18
  52. package/lib/api/response/IIMSStatement.js.map +1 -1
  53. package/lib/api/response/IIMSView.js +16 -18
  54. package/lib/api/response/IIMSView.js.map +1 -1
  55. package/lib/api/response/IIMSViewDBDName.js +16 -18
  56. package/lib/api/response/IIMSViewDBDName.js.map +1 -1
  57. package/lib/api/response/IIMSViewPSBName.js +16 -18
  58. package/lib/api/response/IIMSViewPSBName.js.map +1 -1
  59. package/lib/api/response/IIMSViewRegion.js +16 -18
  60. package/lib/api/response/IIMSViewRegion.js.map +1 -1
  61. package/lib/api/response/IListProfile.js +16 -18
  62. package/lib/api/response/IListProfile.js.map +1 -1
  63. package/lib/api/response/IMonitorList.js +16 -18
  64. package/lib/api/response/IMonitorList.js.map +1 -1
  65. package/lib/api/response/IOverview.js +16 -18
  66. package/lib/api/response/IOverview.js.map +1 -1
  67. package/lib/api/response/IProfileList.js +16 -18
  68. package/lib/api/response/IProfileList.js.map +1 -1
  69. package/lib/api/response/IResponse.js +16 -18
  70. package/lib/api/response/IResponse.js.map +1 -1
  71. package/lib/api/response/ITranview.js +16 -18
  72. package/lib/api/response/ITranview.js.map +1 -1
  73. package/lib/cli/monitor/Monitor.definition.js +16 -18
  74. package/lib/cli/monitor/Monitor.definition.js.map +1 -1
  75. package/lib/cli/monitor/codeview/Codeview.definition.js +16 -18
  76. package/lib/cli/monitor/codeview/Codeview.definition.js.map +1 -1
  77. package/lib/cli/monitor/codeview/Histogram/Histogram.definition.js +33 -22
  78. package/lib/cli/monitor/codeview/Histogram/Histogram.definition.js.map +1 -1
  79. package/lib/cli/monitor/codeview/Histogram/Histogram.handler.js +100 -191
  80. package/lib/cli/monitor/codeview/Histogram/Histogram.handler.js.map +1 -1
  81. package/lib/cli/monitor/codeview/callerid/Callerid.definition.js +16 -18
  82. package/lib/cli/monitor/codeview/callerid/Callerid.definition.js.map +1 -1
  83. package/lib/cli/monitor/codeview/callerid/Callerid.handler.js +16 -18
  84. package/lib/cli/monitor/codeview/callerid/Callerid.handler.js.map +1 -1
  85. package/lib/cli/monitor/codeview/csect/Csect.definition.js +16 -18
  86. package/lib/cli/monitor/codeview/csect/Csect.definition.js.map +1 -1
  87. package/lib/cli/monitor/codeview/csect/Csect.handler.js +16 -18
  88. package/lib/cli/monitor/codeview/csect/Csect.handler.js.map +1 -1
  89. package/lib/cli/monitor/codeview/module/Module.definition.js +16 -18
  90. package/lib/cli/monitor/codeview/module/Module.definition.js.map +1 -1
  91. package/lib/cli/monitor/codeview/module/Module.handler.js +16 -18
  92. package/lib/cli/monitor/codeview/module/Module.handler.js.map +1 -1
  93. package/lib/cli/monitor/db2/DB2.definition.js +16 -18
  94. package/lib/cli/monitor/db2/DB2.definition.js.map +1 -1
  95. package/lib/cli/monitor/db2/db2view/DB2View.definition.js +16 -18
  96. package/lib/cli/monitor/db2/db2view/DB2View.definition.js.map +1 -1
  97. package/lib/cli/monitor/db2/db2view/DB2View.handler.js +16 -18
  98. package/lib/cli/monitor/db2/db2view/DB2View.handler.js.map +1 -1
  99. package/lib/cli/monitor/db2/sqlview/SQLView.definition.js +16 -18
  100. package/lib/cli/monitor/db2/sqlview/SQLView.definition.js.map +1 -1
  101. package/lib/cli/monitor/db2/sqlview/SQLView.handler.js +16 -18
  102. package/lib/cli/monitor/db2/sqlview/SQLView.handler.js.map +1 -1
  103. package/lib/cli/monitor/delayview/Delayview.definition.js +16 -18
  104. package/lib/cli/monitor/delayview/Delayview.definition.js.map +1 -1
  105. package/lib/cli/monitor/delayview/address/Address.definition.js +16 -18
  106. package/lib/cli/monitor/delayview/address/Address.definition.js.map +1 -1
  107. package/lib/cli/monitor/delayview/address/Address.handler.js +16 -18
  108. package/lib/cli/monitor/delayview/address/Address.handler.js.map +1 -1
  109. package/lib/cli/monitor/delayview/delay/Delay.definition.js +16 -18
  110. package/lib/cli/monitor/delayview/delay/Delay.definition.js.map +1 -1
  111. package/lib/cli/monitor/delayview/delay/Delay.handler.js +16 -18
  112. package/lib/cli/monitor/delayview/delay/Delay.handler.js.map +1 -1
  113. package/lib/cli/monitor/history/History.definition.js +16 -18
  114. package/lib/cli/monitor/history/History.definition.js.map +1 -1
  115. package/lib/cli/monitor/history/History.handler.js +16 -18
  116. package/lib/cli/monitor/history/History.handler.js.map +1 -1
  117. package/lib/cli/monitor/idms/IDMS.definition.js +16 -18
  118. package/lib/cli/monitor/idms/IDMS.definition.js.map +1 -1
  119. package/lib/cli/monitor/idms/dml/DML.definition.js +16 -18
  120. package/lib/cli/monitor/idms/dml/DML.definition.js.map +1 -1
  121. package/lib/cli/monitor/idms/dml/DML.handler.js +16 -18
  122. package/lib/cli/monitor/idms/dml/DML.handler.js.map +1 -1
  123. package/lib/cli/monitor/idms/module/IDMSModule.definition.js +16 -18
  124. package/lib/cli/monitor/idms/module/IDMSModule.definition.js.map +1 -1
  125. package/lib/cli/monitor/idms/module/IDMSModule.handler.js +16 -18
  126. package/lib/cli/monitor/idms/module/IDMSModule.handler.js.map +1 -1
  127. package/lib/cli/monitor/idms/task/IDMSTask.definition.js +16 -18
  128. package/lib/cli/monitor/idms/task/IDMSTask.definition.js.map +1 -1
  129. package/lib/cli/monitor/idms/task/IDMSTask.handler.js +16 -18
  130. package/lib/cli/monitor/idms/task/IDMSTask.handler.js.map +1 -1
  131. package/lib/cli/monitor/ims/IMS.definition.js +16 -18
  132. package/lib/cli/monitor/ims/IMS.definition.js.map +1 -1
  133. package/lib/cli/monitor/ims/dbdname/DBDName.definition.js +16 -18
  134. package/lib/cli/monitor/ims/dbdname/DBDName.definition.js.map +1 -1
  135. package/lib/cli/monitor/ims/dbdname/DBDName.handler.js +16 -18
  136. package/lib/cli/monitor/ims/dbdname/DBDName.handler.js.map +1 -1
  137. package/lib/cli/monitor/ims/imsview/IMSView.definition.js +16 -18
  138. package/lib/cli/monitor/ims/imsview/IMSView.definition.js.map +1 -1
  139. package/lib/cli/monitor/ims/imsview/IMSView.handler.js +16 -18
  140. package/lib/cli/monitor/ims/imsview/IMSView.handler.js.map +1 -1
  141. package/lib/cli/monitor/ims/psbname/PSBName.definition.js +16 -18
  142. package/lib/cli/monitor/ims/psbname/PSBName.definition.js.map +1 -1
  143. package/lib/cli/monitor/ims/psbname/PSBName.handler.js +16 -18
  144. package/lib/cli/monitor/ims/psbname/PSBName.handler.js.map +1 -1
  145. package/lib/cli/monitor/ims/region/Region.definition.js +16 -18
  146. package/lib/cli/monitor/ims/region/Region.definition.js.map +1 -1
  147. package/lib/cli/monitor/ims/region/Region.handler.js +16 -18
  148. package/lib/cli/monitor/ims/region/Region.handler.js.map +1 -1
  149. package/lib/cli/monitor/ims/ssa/SSA.definition.js +16 -18
  150. package/lib/cli/monitor/ims/ssa/SSA.definition.js.map +1 -1
  151. package/lib/cli/monitor/ims/ssa/SSA.handler.js +16 -18
  152. package/lib/cli/monitor/ims/ssa/SSA.handler.js.map +1 -1
  153. package/lib/cli/monitor/ims/statement/Statement.definition.js +16 -18
  154. package/lib/cli/monitor/ims/statement/Statement.definition.js.map +1 -1
  155. package/lib/cli/monitor/ims/statement/Statement.handler.js +16 -18
  156. package/lib/cli/monitor/ims/statement/Statement.handler.js.map +1 -1
  157. package/lib/cli/monitor/overview/Overview.definition.js +16 -18
  158. package/lib/cli/monitor/overview/Overview.definition.js.map +1 -1
  159. package/lib/cli/monitor/overview/Overview.handler.js +16 -18
  160. package/lib/cli/monitor/overview/Overview.handler.js.map +1 -1
  161. package/lib/cli/monitor/tranview/Tranview.definition.js +16 -18
  162. package/lib/cli/monitor/tranview/Tranview.definition.js.map +1 -1
  163. package/lib/cli/monitor/tranview/all/All.definition.js +16 -18
  164. package/lib/cli/monitor/tranview/all/All.definition.js.map +1 -1
  165. package/lib/cli/monitor/tranview/all/All.handler.js +16 -18
  166. package/lib/cli/monitor/tranview/all/All.handler.js.map +1 -1
  167. package/lib/cli/monitor/tranview/callerid/Callerid.definition.js +16 -18
  168. package/lib/cli/monitor/tranview/callerid/Callerid.definition.js.map +1 -1
  169. package/lib/cli/monitor/tranview/callerid/Callerid.handler.js +16 -18
  170. package/lib/cli/monitor/tranview/callerid/Callerid.handler.js.map +1 -1
  171. package/lib/cli/monitor/tranview/callstack/CallStack.definition.js +16 -18
  172. package/lib/cli/monitor/tranview/callstack/CallStack.definition.js.map +1 -1
  173. package/lib/cli/monitor/tranview/callstack/CallStack.handler.js +16 -18
  174. package/lib/cli/monitor/tranview/callstack/CallStack.handler.js.map +1 -1
  175. package/lib/cli/monitor/tranview/csect/CsectDetail.definition.js +16 -18
  176. package/lib/cli/monitor/tranview/csect/CsectDetail.definition.js.map +1 -1
  177. package/lib/cli/monitor/tranview/csect/CsectDetail.handler.js +16 -18
  178. package/lib/cli/monitor/tranview/csect/CsectDetail.handler.js.map +1 -1
  179. package/lib/cli/monitor/tranview/delay/DelayDetail.definition.js +16 -18
  180. package/lib/cli/monitor/tranview/delay/DelayDetail.definition.js.map +1 -1
  181. package/lib/cli/monitor/tranview/delay/DelayDetail.handler.js +16 -18
  182. package/lib/cli/monitor/tranview/delay/DelayDetail.handler.js.map +1 -1
  183. package/lib/cli/monitor/tranview/module/Module.definition.js +16 -18
  184. package/lib/cli/monitor/tranview/module/Module.definition.js.map +1 -1
  185. package/lib/cli/monitor/tranview/module/Module.handler.js +16 -18
  186. package/lib/cli/monitor/tranview/module/Module.handler.js.map +1 -1
  187. package/lib/cli/monitor/tranview/stat/Cicstat.definition.js +16 -18
  188. package/lib/cli/monitor/tranview/stat/Cicstat.definition.js.map +1 -1
  189. package/lib/cli/monitor/tranview/stat/Cicstat.handler.js +16 -18
  190. package/lib/cli/monitor/tranview/stat/Cicstat.handler.js.map +1 -1
  191. package/lib/cli/profile/Profile.definition.js +16 -18
  192. package/lib/cli/profile/Profile.definition.js.map +1 -1
  193. package/lib/cli/profile/create/CreateProfile.definition.js +16 -18
  194. package/lib/cli/profile/create/CreateProfile.definition.js.map +1 -1
  195. package/lib/cli/profile/create/CreateProfile.handler.js +16 -18
  196. package/lib/cli/profile/create/CreateProfile.handler.js.map +1 -1
  197. package/lib/cli/profile/invoke/InvokeProfile.definition.js +16 -18
  198. package/lib/cli/profile/invoke/InvokeProfile.definition.js.map +1 -1
  199. package/lib/cli/profile/invoke/InvokeProfile.handler.js +16 -18
  200. package/lib/cli/profile/invoke/InvokeProfile.handler.js.map +1 -1
  201. package/lib/cli/profile/listprofile/ListProfile.definition.js +16 -18
  202. package/lib/cli/profile/listprofile/ListProfile.definition.js.map +1 -1
  203. package/lib/cli/profile/listprofile/ListProfile.handler.js +16 -18
  204. package/lib/cli/profile/listprofile/ListProfile.handler.js.map +1 -1
  205. package/lib/cli/session/EndevorSession.d.ts +33 -0
  206. package/lib/cli/session/EndevorSession.js +120 -0
  207. package/lib/cli/session/EndevorSession.js.map +1 -0
  208. package/lib/cli/session/MATSession.js +16 -18
  209. package/lib/cli/session/MATSession.js.map +1 -1
  210. package/lib/handlers/AbstractAnalyzeHandler.js +16 -18
  211. package/lib/handlers/AbstractAnalyzeHandler.js.map +1 -1
  212. package/lib/handlers/AbstractGetHandler.js +16 -18
  213. package/lib/handlers/AbstractGetHandler.js.map +1 -1
  214. package/lib/handlers/AbstractObjectDisplayHandler.js +16 -18
  215. package/lib/handlers/AbstractObjectDisplayHandler.js.map +1 -1
  216. package/lib/handlers/AbstractPostHandler.js +16 -18
  217. package/lib/handlers/AbstractPostHandler.js.map +1 -1
  218. package/lib/handlers/AbstractProfileActionHandler.js +16 -18
  219. package/lib/handlers/AbstractProfileActionHandler.js.map +1 -1
  220. package/lib/handlers/AbstractRestHandler.js +16 -18
  221. package/lib/handlers/AbstractRestHandler.js.map +1 -1
  222. package/lib/handlers/AbstractTableDisplayHandler.js +16 -18
  223. package/lib/handlers/AbstractTableDisplayHandler.js.map +1 -1
  224. package/lib/healthCheck.Handler.js +10 -6
  225. package/lib/healthCheck.Handler.js.map +1 -1
  226. package/lib/imperative.js +16 -18
  227. package/lib/imperative.js.map +1 -1
  228. package/lib/index.js +16 -18
  229. package/lib/index.js.map +1 -1
  230. package/package.json +1 -1
package/README.md CHANGED
@@ -1,1494 +1,1514 @@
1
- <img src="https://artwork.openmainframeproject.org/other/zowe-conformant/zowev2/cli/color/zowe-conformant-zowev2-cli-color.png" width="100" height="75" alt="Zowe Conformance Badge">
2
-
3
- # MAT Analyze Plug-in for Zowe CLI
4
-
5
- The MAT Analyze plug-in for Zowe CLI provides access to Mainframe Application Tuner (MAT) functionality. The plug-in ensures interaction with MAT and enables you to measure your mainframe applications and get the analysis data in the form of MAT analysis views using Zowe command line interface.
6
-
7
- You can use the MAT Analyze plug-in for Zowe CLI to perform the following tasks:
8
-
9
- - Manage monitor profiles.
10
- Create and invoke monitor profiles, view the lists of available profiles, and retrieve the measurement history.
11
- - Analyze the measurement data.
12
- Access the measurement data from Mainframe Application Tuner that is available to you in the CLI in the form of MAT analysis views.
13
- - Address performance issues.
14
- With the source program listing registered with MAT, users of Visual Studio Code (VS Code) IDE can obtain the Histogram details and display specific source program locations that are associated with the most resource-consuming program modules and CSECTs. When you request the Histogram measurement details from your VS Code command line terminal, the MAT Analyze plug-in for Zowe CLI transfers the source code listing to your local machine and navigates you directly to the specific line and column number of the source code, which enables you to immediately inspect the program statement and identify possible tuning opportunities.
15
-
16
- # Table of Contents
17
-
18
- - [Installation](#installation)
19
- - [Prerequisites](#prerequisites)
20
- - [Install the MAT Analyze Plug-in for Zowe CLI From Packages](#install-the-mat-analyze-plug-in-for-zowe-cli-from-packages)
21
- - [Validate the Installation](#validate-the-installation)
22
- - [Create a MAT Profile](#create-a-mat-profile)
23
- - [Use MAT Profile Options](#use-mat-profile-options)
24
- - [Use Cases and Commands](#use-cases-and-commands)
25
- - [PROFILE](#profile)
26
- - [create | cr](#create--cr)
27
- - [invoke | ivk](#invoke--ivk)
28
- - [list | lip](#list--lip)
29
- - [MONITOR](#monitor)
30
- - [history | hs](#history--hs)
31
- - [overview | ov](#overview--ov)
32
- - [delayview](#delayview)
33
- - [delay | de](#delay--de)
34
- - [address | ad](#address--ad)
35
- - [codeview](#codeview)
36
- - [module | mod](module--mod)
37
- - [csect | cs](#csect--cs)
38
- - [histogram | hsg](#histogram--hsg)
39
- - [callerid | cil](#callerid--cil)
40
- - [db2](#db2)
41
- - [db2view | db2](#db2view--db2)
42
- - [sqlstmt | sql](#sqlstmt--sql)
43
- - [idms](#idms)
44
- - [dml | dml](#dml--dml)
45
- - [module | mod](#idms)
46
- - [task | ts](#task--ts)
47
- - [ims](#ims)
48
- - [dbdname | dbd](#dbdname--dbd)
49
- - [imsview | imsv](#imsview--imsv)
50
- - [psbname | psb](#psbname--psb)
51
- - [region | reg](#region--reg)
52
- - [ssa | ssa](#ssa--ssa)
53
- - [statement | stat](#statement--stat)
54
- - [tranview](#tranview)
55
- - [all | all](#all--all)
56
- - [module | mod](#tranview)
57
- - [callerid | cid](#callerid--cid)
58
- - [callstack | csk](#callstack--csk)
59
- - [csect | csd](#csect--csd)
60
- - [delay | dl](#delay--dl)
61
- - [stat | cis](#stat--cis)
62
- - [Uninstall the MAT Analyze Plug-in for Zowe CLI](#uninstall-the-mat-analyze-plug-in-for-zowe-cli)
63
-
64
- # Installation
65
-
66
- You can install the MAT Analyze Plug-in for Zowe CLI from the Zowe Package.
67
-
68
- ## Prerequisites
69
-
70
- Before starting the installation of the MAT Analyze Plug-in for Zowe CLI, verify that you have:
71
-
72
- - Zowe version 2 (Zowe CLI version 7.x) is installed.
73
- - MAT database and the REST API installed, configured, and running.
74
- - (Optional) To use the automated listing registration and retrieval option through Endevor® footprints, install and configure the Endevor® Web Services and specify the Endevor® web server details in the MAT database configuration.
75
-
76
- ## Install the MAT Analyze Plug-in for Zowe CLI From Packages
77
-
78
- Issue the following command:
79
-
80
- ```
81
- $ zowe plugins install @broadcom/mat-analyze-for-zowe-cli
82
- ```
83
-
84
- **Note:**
85
- The `latest` npm tag installs a version of the product that is intended for public consumption. You can use different npm tags to install other versions of the product. For example, you can install with the `@beta` tag to try new features that have not been fully validated. For more information about tag usage, see [NPM Tag Names](https://github.com/zowe/zowe-cli/blob/master/docs/MaintainerVersioning.md#npm-tag-names).
86
-
87
- ## Validate the Installation
88
-
89
- To validate the installation, issue the following command:
90
-
91
- ```
92
- $ zowe plugins validate @broadcom/mat-analyze-for-zowe-cli
93
- ```
94
-
95
- Successful validation of the plug-in returns the response "This plugin was successfully validated. Enjoy the plugin."
96
-
97
- ## Create a MAT Profile
98
-
99
- To enable the interaction of the MAT Analyze plug-in for Zowe CLI with MAT, you need to specify the MAT profile details that include the protocol type, host, and port that you defined for the MAT REST API server, and your mainframe username and password. The details of the MAT profile are stored in the Zowe configuration file. To create a global Zowe configuration file, use the command `zowe config init --global-config`, then edit the configuration file and add a section with the MAT profile details:
100
-
101
- ```
102
- "mat": {
103
-             "type": "mat",
104
-             "properties": {
105
-                 "host": "example.com",
106
-                 "protocol": "http",
107
-                 "port": "12345",
108
-                 "user": "johndoe",
109
-                 "password": "qwerty",
110
-                 "listingDir": "c:\listings",
111
-                 "rejectUnauthorized": false
112
-             },
113
-             "secure": []
114
-         },
115
- ```
116
-
117
- ## Use MAT Profile Options
118
-
119
- `--protocol` | `--o` _(string)_
120
- Specifies the protocol defined for the MAT REST API server (http or https).
121
- Allowed values: http, https.
122
-
123
- `--host` | `--H` _(string)_
124
- Specifies the hostname or IP address defined for the MAT REST API server (e.g. 127.0.0.0 or localhost).
125
-
126
- `--port` | `--P` _(number)_
127
- Specifies the server port (e.g. 8080).
128
-
129
- `--user` | `--u` _(string)_
130
- Your mainframe username.
131
-
132
- `--password` | `--pw` _(string)_
133
- Your mainframe password.
134
-
135
- `--base-path` | `--bp` _(string)_
136
- The base path for your API mediation layer instance. Specify this option to prepend the base path to all resources when making REST requests. Do not specify this option if you are not using an API mediation layer.
137
-
138
- `--reject-unauthorized` | `--ru` _(boolean)_
139
- Reject self-signed certificates.
140
- Default value: true
141
-
142
- `--listingDir` | `--ldir` _(string)_
143
- Specifies the directory where you want to store the registered program listings (e.g. 'c:\listings') for your immediate source code inspection. You can use the advantage of automated listing registration with MAT and listing retrieval through Endevor® footprints for Cobol, C/C++, and Assembler programs. When a source program listing is registered with MAT, you can enhance the histogram analysis data with the program listing details that pertain to the specific CSECT and program statement. The listing is transfered to the specified directory, which enables you to navigate directly to the line of the source code in you VS Code IDE and inspect the program statement. To use the listing retrieval option through Endevor® footprints, you need to have the Endevor® Web Services installed and configured and specify the Endevor® web server details in the MAT database configuration. The `--listingDir` parameter is optional.
144
-
145
- If the details are not specified or if you want to temporarily use different MAT profile settings, you can specify all or some MAT profile details with each command. The MAT profile details that are provided with a command have the highest priority and override all other values. For more information about using profiles in Zowe, see [Using Global Profile Configuration](https://docs.zowe.org/stable/user-guide/cli-using-global-profile-configuration/) in the Zowe documentation.
146
-
147
- # Use Cases and Commands
148
-
149
- The MAT Analyze plug-in for Zowe CLI enables you to manage monitor profiles and get the measurement analysis data using Mainframe Application Tuner (MAT).
150
-
151
- ```
152
- $ zowe mat <group>
153
- ```
154
-
155
- The MAT Analyze plug-in for Zowe CLI commands are organized in the following **command groups**:
156
-
157
- ## PROFILE
158
-
159
- The commands from the PROFILE group enable you to create, invoke, and list MAT monitor profiles.
160
-
161
- **Usage**
162
-
163
- ```
164
- $ zowe mat profile <command>
165
- ```
166
-
167
- The following **commands** are available for the PROFILE group:
168
-
169
- ### create | cr
170
-
171
- Create a MAT monitor profile.
172
-
173
- **Usage**
174
-
175
- ```
176
- $ zowe mat profile create [options]
177
- ```
178
-
179
- **Required Options**
180
- `--profile` _(string)_
181
- Specifies the name of the profile that you create in MAT (e.g. PROFILE1).
182
- Values: 1 to 8 characters, a combination of alphanumeric and national characters (A-Z, 0-9, and @), the first character must be an alphabetic or @. The profile name must not contain characters # and $.
183
-
184
- `--jobname` _(string)_
185
- Specifies the name of the job that you want to measure (e.g. JOB1).
186
- Values: 1 to 8 characters, alphanumeric (A-Z capitals only and 0-9), national (#, $, @), and wildcards (\* or %).
187
-
188
- `--targsys` _(string)_
189
- Specifies the target system in SYSPLEX.
190
- Values: a comma separated list of up to 4 values is allowed, 1-8 characters each, a combination of alphanumeric (A-Z and 0-9) and national (@,#,$), the first character must be an alphabetic (A-Z) or a national (@, #, $), e.g. AA31,AA32).
191
-
192
- **Options**
193
- `--batchreports` _(string)_
194
- Specifies the setting for the Batch report option upon monitor completion.
195
- Default value: no.
196
- Allowed values: yes, no.
197
-
198
- `--description` _(string)_
199
- Provide the monitor description (maximum 24 characters).
200
-
201
- `--mondsn` _(string)_
202
- Specifies the monitor data set name where MAT saves the measurement (e.g. DEMO.MAT.MONITOR).
203
- Values: data set name pattern, maximum 46 characters. If not specified, your default MAT monitor DSN pattern is applied.
204
-
205
- `--stepname` _(string)_
206
- Specifies the name of the job step to monitor.
207
- Values: maximum 8 characters, alphanumeric (A-Z capitals only and 0-9), national (#, $, @), and wildcards (\* or %).
208
-
209
- `--mstep` _(string)_
210
- Indicates whether the multi-step monitoring option is enabled.
211
- Default value: no.
212
- Allowed values: yes, no.
213
-
214
- `--procstep` _(string)_
215
- Specifies the name of the procedure step.
216
- Values: maximum 8 characters, alphanumeric (A-Z capitals only and 0-9), national (#, $, @), and wildcards (\* or %).
217
-
218
- `--program` _(string)_
219
- Specifies the name of the program to monitor.
220
- Values: maximum 8 characters, alphanumeric (A-Z capitals only and 0-9), national (#, $, @), and wildcards (\* or %).
221
-
222
- `--elapstime` _(string)_
223
- Specifies the required monitor duration followed by s (seconds) or m (minutes) (e.g. 60s).
224
- Values: maximum 6 characters total, number must be > 0.
225
- Default value: 60s.
226
-
227
- `--smon` _(string)_
228
- Specifies whether to monitor the entire step.
229
- Default value: no.
230
- Allowed values: yes, no.
231
-
232
- `--tasklib` _(string)_
233
- Specifies an additional DD name for load modules.
234
- Values: maximum 8 characters, alphanumeric (A-Z capitals only and 0-9), national (#, $, @), and wildcards (\* or %).
235
-
236
- `--samplecnt` _(string)_
237
- Specifies the number of observations requested.
238
- Values: maximum 6 characters, numbers between 10 and 999999.
239
- Default value: 6000.
240
-
241
- `--succnt` _(string)_
242
- Specifies the maximum number of monitors to run per job execution. Values: maximum 4 characters, numbers between 1 and 9999.
243
- Default value: 1.
244
-
245
- `--reccnt` _(string)_
246
- Specifies the number of times this job step will be monitored. Values: maximum 4 characters, numbers between 1 and 9999.
247
- Default value: 1.
248
-
249
- `--sampdelay` _(string)_
250
- Specifies the delay monitoring time in seconds after the step start. Values: maximum 4 characters, numbers between 0 and 9999.
251
- Default value: 0.
252
-
253
- `--userexit1` _(string)_
254
- Specifies the name for the call user written Data Base.
255
- Values: maximum 8 characters, alphanumeric (A-Z capitals only and 0-9), national (#, $, @), and wildcards (\* or %) (e.g. DBEXIT1).
256
-
257
- `--userexit2` _(string)_
258
- Specifies the name 1 for the call user written 4GL exit programs for this monitor.
259
- Values: maximum 8 characters, alphanumeric (A-Z capitals only and 0-9), national (#, $, @), and wildcards (\* or %) (e.g. UEXIT1).
260
-
261
- `--userexit3` _(string)_
262
- Specifies the name 2 for the call user written 4GL exit programs for this monitor.
263
- Values: maximum 8 characters, alphanumeric (A-Z capitals only and 0-9), national (#, $, @), and wildcards (\* or %) (e.g. UEXIT2).
264
-
265
- `--inctask` _(string)_
266
- Specifies the task name to define the tasks that you want to sample in a multitasking environment and restrict monitoring to the specific subtask within the address space.
267
- Values: a comma separated list of up to 4 values is allowed, maximum 8 characters each, alphanumeric (A-Z capitals only and 0-9), national (#, $, @), and wildcards (\* or %) (e.g. INC31,INC32).
268
-
269
- `--exctask` _(string)_
270
- Specifies the task name to omit from sampling in a multitasking environment.
271
- Values: a comma separated list of up to 4 values is allowed, max. 8 characters each, alphanumeric (A-Z capitals only and 0-9), national (#, $, @), and wildcards (\* or %) (e.g. EXC31,EXC32).
272
-
273
- `--tran` _(string)_
274
- Specifies the CICS transaction code name to monitor.
275
- Values: a comma separated list of up to 4 values is allowed, maximum 8 characters each, alphanumeric (A-Z capitals only and 0-9), national (#, $, @), and wildcards (\* or +) (e.g. TRAN1,TRAN2).
276
-
277
- `--term` _(string)_
278
- Specifies the CICS terminal IDs to monitor.
279
- Values: a comma separated list of up to 4 values is allowed, maximum 8 characters each, alphanumeric (A-Z capitals only and 0-9), national (#, $, @), and wildcards (\* or +) (e.g. TERM1,TERM2).
280
-
281
- `--userid` _(string)_
282
- Specifies the CICS user IDs to monitor.
283
- Values: a comma separated list of up to 4 values is allowed, maximum 8 characters each, alphanumeric (A-Z capitals only and 0-9), national (#, $, @), and wildcards (\* or +) (e.g. USER1,USER2).
284
-
285
- `--db2expl` _(string)_
286
- Indicates whether the Explain SQL option is enabled for DB2 SQL statements.
287
- Default value: no.
288
- Allowed values: yes, no.
289
-
290
- `--db2ctsql` _(string)_
291
- Indicates whether the Collect SQL from Catalog option is enabled for DB2 SQL statements. If you specify db2expl=yes, then db2ctsql must be also set to yes.
292
- Default value: no.
293
- Allowed values: yes, no.
294
-
295
- `--db2hvloc` _(string)_
296
- Indicates whether the Requestor Location option is enabled for DB2 measurements.
297
- Default value: no.
298
- Allowed values: yes, no.
299
-
300
- `--db2hvcor` _(string)_
301
- Indicates whether the Correlation ID option for SQL statements is enabled for DB2 measurements.
302
- Default value: no.
303
- Allowed values: yes, no.
304
-
305
- `--db2hviid` _(string)_
306
- Indicates whether the Operator ID option for SQL statements is enabled for DB2 measurements.
307
- Default value: no.
308
- Allowed values: yes, no.
309
-
310
- `--db2hvthd` _(string)_
311
- Indicates whether the Thread Address option for SQL statements is enabled for DB2 measurements.
312
- Default value: no.
313
- Allowed values: yes, no.
314
-
315
- `--wasexprt` _(string)_
316
- Indicates whether the Expert Mode is enabled for Java measurement.
317
- Default value: no.
318
- Allowed values: yes, no.
319
-
320
- `--urlfilt` _(string)_
321
- A filtering string to restrict monitoring to the specific application URL, transaction, or stored procedure for Java measurements.
322
- Values: a comma separated list of up to 4 values is allowed, max. 64 characters (e.g. mypage1.html,mypage2.html).
323
-
324
- `--sysfilt` _(string)_
325
- A filtering string to include the specified system class for Java measurements. If you specify a value for sysfilt, the measurement includes only the classes that match the filtering string pattern.
326
- Values: a comma separated list of up to 3 values is allowed, max. 64 characters (e.g. user1.class,user2.class).
327
-
328
- `--schedule` _(string)_
329
- Specifies the name of the schedule that you want to apply to the monitor profile (maximum 8 characters).
330
-
331
- **Examples**
332
-
333
- - Create the PROFILE1 monitor profile to measure job JOB1 that runs on the AA31 system:
334
-
335
- ```
336
- $ zowe mat profile create --profile PROFILE1 --jobname JOB1 --targsys AA31
337
- ```
338
-
339
- - Create the PROFILE1 monitor profile to measure for 90 seconds job JOB1 that runs on the AA31 and AA32 systems:
340
-
341
- ```
342
- $ zowe mat profile create --profile PROFILE1 --jobname JOB1 --targsys AA31,AA32 --elapstime 90s
343
- ```
344
-
345
- - Create the PROFILE1 monitor profile to measure job JOB1 that runs on the AA31 system, with the specific MAT profile details defined:
346
-
347
- ```
348
- $ zowe mat profile create --profile PROFILE1 --jobname JOB1 --targsys AA31 --host "example.com" --port 12345 --user johndoe --password qwerty
349
- ```
350
-
351
- ### invoke | ivk
352
-
353
- Invoke a MAT monitor profile to start measurement. If you invoke a monitor profile that does currently exist, MAT creates the profile with the provided name and invokes the measurement for this profile.
354
-
355
- **Usage**
356
-
357
- ```
358
- $ zowe mat profile invoke [options]
359
- ```
360
-
361
- **Required Options**
362
- `--profile` _(string)_
363
- Specifies the name of the profile in MAT that you invoke (e.g. PROFILE1).
364
- Values: 1 to 8 characters, a combination of alphanumeric and national characters (A-Z, 0-9, and @), the first character must be an alphabetic or @. The profile name must not contain characters # and $.
365
-
366
- `--jobname` _(string)_
367
- Specifies the name of the job to be measured (e.g. JOB1).
368
- Values: 1 to 8 characters, alphanumeric (A-Z capitals only and 0-9), national (#, $, @), and wildcards (\* or %).
369
-
370
- `--targsys` _(string)_
371
- Specifies the target system in SYSPLEX.
372
- Values: a comma separated list of up to 4 values is allowed, maximum 8 characters each, a combination of alphanumeric (A-Z and 0-9) and national (@,#,$), the first character must be an alphabetic (A-Z) or a national (@, #, $) (e.g. AA31,AA32).
373
-
374
- **Options**
375
- `--mondsn` _(string)_
376
- Specifies the monitor data set name where MAT saves the measurement (e.g. DEMO.MAT.MONITOR).
377
- Values: data set name pattern, maximum 46 characters. If not specified, your default MAT monitor DSN pattern is applied.
378
-
379
- `--moiuuid` _(string)_
380
- Specifies the MOI UUID.
381
- Values: maximum 61 characters, alphanumeric (A-Z and 0-9). If you use this parameter for command execution, the value cannot be blank.
382
-
383
- `--moitimestamp` _(string)_
384
- Specifies the MOI timestamp.
385
- Values: maximum 12 characters, numbers only (0-9). If you use this parameter for command execution, the value cannot be blank.
386
-
387
- `--listing` _(boolean)_
388
- Activates automated registration of Cobol, C/C++, and Assembler program listings through Endevor® footprints. After completion of the measurement that you invoke with the '--listing' parameter, the MAT Analyze plug-in for Zowe CLI automatically retrieves the program listing that is associated with the monitored job and registers the listing with MAT. A registered program listing enhances the analysis possibilities of the 'codeview histogram' command and enables you to inspect the source code statements that are associated with specific modules and CSECTs.
389
-
390
- **Examples**
391
-
392
- - Invoke the PROFILE1 monitor profile to measure job JOB1 that runs on the AA31 system:
393
-
394
- ```
395
- $ zowe mat profile invoke --profile PROFILE1 --jobname JOB1 --targsys AA31
396
- ```
397
-
398
- - Invoke the PROFILE1 monitor profile to measure job JOB1 that runs on the AA31 system and save the measurement result in the DEMO.MAT.MONITOR.PROFILE1 data set:
399
-
400
- ```
401
- $ zowe mat profile invoke --profile PROFILE1 --jobname JOB1 --targsys AA31 --mondsn DEMO.MAT.MONITOR.PROFILE1
402
- ```
403
-
404
- - Invoke the PROFILE1 monitor profile to measure job JOB1 that runs on the AA31 system and register the program listing:
405
-
406
- ```
407
- $ zowe mat profile invoke --profile PROFILE1 --jobname JOB1 --targsys AA31 --listing
408
- ```
409
-
410
- - Invoke the PROFILE1 monitor profile to measure job JOB1 that runs on the AA31 system, with the specific MAT profile details defined:
411
-
412
- ```
413
- $ zowe mat profile invoke --profile PROFILE1 --jobname JOB1 --targsys AA31 --host "example.com" --port 12345 --user johndoe --password qwerty
414
- ```
415
-
416
- ### list | lip
417
-
418
- Get the list of available monitor profiles.
419
-
420
- **Usage**
421
-
422
- ```
423
- $ zowe mat profile list [options]
424
- ```
425
-
426
- ## MONITOR
427
-
428
- The commands from the MONITOR group enable you to get monitor history and measurement analysis data from MAT.
429
-
430
- **Usage**
431
-
432
- ```
433
- $ zowe mat monitor <command|group>
434
- ```
435
-
436
- The following **commands** are available for the MONITOR group:
437
-
438
- ### history | hs
439
-
440
- Get the list of all available measurements that are stored in the history of the specific monitor profile.
441
-
442
- **Usage**
443
-
444
- ```
445
- $ zowe mat monitor history [options]
446
- ```
447
-
448
- **Options**
449
- `--profile` _(string)_
450
- Specifies the name of the profile.
451
-
452
- **Examples**
453
-
454
- - Get the list of all available measurements that are stored in the history of the monitor profile TESTPROF:
455
-
456
- ```
457
- $ zowe mat monitor history --profile TESTPROF
458
- ```
459
-
460
- - Get the list of all available measurements that are stored in the history of the monitor profile TESTPROF, with the specific MAT profile details defined:
461
-
462
- ```
463
- $ zowe mat monitor history --profile TESTPROF --host "example.com" --port 12345 --user johndoe --password qwerty
464
- ```
465
-
466
- ### overview | ov
467
-
468
- Get the Overview details of the measurement.
469
-
470
- **Usage**
471
-
472
- ```
473
- $ zowe mat monitor overview [options]
474
- ```
475
-
476
- **Options**
477
- `--profile` _(string)_
478
- Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
479
-
480
- `--mon_num` _(number)_
481
- Specifies the unique monitor number of the measurement.
482
-
483
- **Examples**
484
-
485
- - Get the measurement overview details for monitor number 5:
486
-
487
- ```
488
- $ zowe mat monitor overview --mon_num 5
489
- ```
490
-
491
- - Get the measurement overview details for the latest monitor in the TESTPROF profile:
492
-
493
- ```
494
- $ zowe mat monitor overview --profile TESTPROF
495
- ```
496
-
497
- - Get the measurement overview details for monitor number 5, with the specific MAT profile details defined:
498
-
499
- ```
500
- $ zowe mat monitor overview --mon_num 5 --host "example.com" --port 12345 --user johndoe --password qwerty
501
- ```
502
-
503
- The following **subgroups** are available for the MONITOR command group:
504
-
505
- ### delayview
506
-
507
- The commands from the DELAYVIEW group enable you to get the DelayView measurement details.
508
-
509
- **Usage**
510
-
511
- ```
512
- $ zowe mat monitor delayview <command>
513
- ```
514
-
515
- The following **commands** are available for the DELAYVIEW group:
516
-
517
- #### delay | de
518
-
519
- Get the delay details for the measurement.
520
-
521
- **Usage**
522
-
523
- ```
524
- $ zowe mat monitor delayview delay [options]
525
- ```
526
-
527
- **Options**
528
- `--profile` _(string)_
529
- Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
530
-
531
- `--mon_num` _(number)_
532
- Specifies the unique monitor number of the measurement.
533
-
534
- **Examples**
535
-
536
- - Get the DelayView measurement details for monitor number 5:
537
-
538
- ```
539
- $ zowe mat monitor delayview delay --mon_num 5
540
- ```
541
-
542
- - Get the DelayView measurement details for the latest monitor in the TESTPROF profile:
543
-
544
- ```
545
- $ zowe mat monitor delayview delay --profile TESTPROF
546
- ```
547
-
548
- - Get the DelayView measurement details for monitor number 5, with the specific MAT profile details defined:
549
-
550
- ```
551
- $ zowe mat monitor delayview delay --mon_num 5 --host "example.com" --port 12345 --user johndoe --password qwerty
552
- ```
553
-
554
- #### address | ad
555
-
556
- Get the delay address details for the measurement.
557
-
558
- **Usage**
559
-
560
- ```
561
- $ zowe mat monitor delayview address [options]
562
- ```
563
-
564
- **Options**
565
- `--profile` _(string)_
566
- Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
567
-
568
- `--mon_num` _(number)_
569
- Specifies the unique monitor number of the measurement.
570
-
571
- `--majorcategory` _(string)_
572
- Specifies the major delay category name identified for the analysis item (e.g. `--majorcategory "PC routine delay"`). You get the majorcategory value from the 'delayview delay' command response.
573
-
574
- `--minorcategory` _(string)_
575
- Specifies the minor delay category name identified for the analysis item (e.g. `--minorcategory "PC CALL"`). You get the minorcategory value from the 'delayview delay' command response.
576
-
577
- **Examples**
578
-
579
- - Get the delay address details for majorcategory "PC routine delay" and minorcategory "PC CALL" for monitor number 5:
580
-
581
- ```
582
- $ zowe mat monitor delayview address --mon_num 5 --majorcategory "PC routine delay" --minorcategory "PC CALL"
583
- ```
584
-
585
- - Get the delay address details for majorcategory "PC routine delay" and minorcategory "PC CALL" for the latest monitor in the TESTPROF profile:
586
-
587
- ```
588
- $ zowe mat monitor delayview address --profile TESTPROF --majorcategory "PC routine delay" --minorcategory "PC CALL"
589
- ```
590
-
591
- - Get the delay address details for majorcategory "PC routine delay" and minorcategory "PC CALL" for monitor number 5, with the specific MAT profile details defined:
592
-
593
- ```
594
- $ zowe mat monitor delayview address --mon_num 5 --majorcategory "PC routine delay" --minorcategory "PC CALL" --host "example.com" --port 12345 --user johndoe --password qwerty
595
- ```
596
-
597
- ### codeview
598
-
599
- The commands from the CODEVIEW group enable you to get the CodeView measurement details.
600
-
601
- **Usage**
602
-
603
- ```
604
- $ zowe mat monitor codeview <command>
605
- ```
606
-
607
- The following **commands** are available for the CODEVIEW group:
608
-
609
- #### module | mod
610
-
611
- Get the CodeView measurement details in Module mode.
612
-
613
- **Usage**
614
-
615
- ```
616
- $ zowe mat monitor codeview module [options]
617
- ```
618
-
619
- **Options**
620
- `--profile` _(string)_
621
- Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
622
-
623
- `--mon_num` _(number)_
624
- Specifies the unique monitor number of the measurement.
625
-
626
- **Examples**
627
-
628
- - Get the CodeView measurement details in Module mode for monitor number 5:
629
-
630
- ```
631
- $ zowe mat monitor codeview module --mon_num 5
632
- ```
633
-
634
- - Get the CodeView measurement details in Module mode for the latest monitor in the TESTPROF profile:
635
-
636
- ```
637
- $ zowe mat monitor codeview module --profile TESTPROF
638
- ```
639
-
640
- - Get the CodeView measurement details in Module mode for monitor number 5, with the specific MAT profile details defined:
641
-
642
- ```
643
- $ zowe mat monitor codeview module --mon_num 5 --host "example.com" --port 12345 --user johndoe --password qwerty
644
- ```
645
-
646
- #### csect | cs
647
-
648
- Get the CodeView measurement details in Csect mode.
649
-
650
- **Usage**
651
-
652
- ```
653
- $ zowe mat monitor codeview csect [options]
654
- ```
655
-
656
- **Options**
657
- `--profile` _(string)_
658
- Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
659
-
660
- `--mon_num` _(number)_
661
- Specifies the unique monitor number of the measurement.
662
-
663
- **Examples**
664
-
665
- - Get the CodeView measurement details in Csect mode for monitor number 5:
666
-
667
- ```
668
- $ zowe mat monitor codeview csect --mon_num 5
669
- ```
670
-
671
- - Get the CodeView measurement details in Csect mode for the latest monitor in the TESTPROF profile:
672
-
673
- ```
674
- $ zowe mat monitor codeview csect --profile TESTPROF
675
- ```
676
-
677
- - Get the CodeView measurement details in Csect mode for monitor number 5, with the specific MAT profile details defined:
678
-
679
- ```
680
- $ zowe mat monitor codeview csect --mon_num 5 --host "example.com" --port 12345 --user johndoe --password qwerty
681
- ```
682
-
683
- #### histogram | hsg
684
-
685
- Get the Histogram details for the measurement.
686
-
687
- **Usage**
688
-
689
- ```
690
- $ zowe mat monitor codeview histogram [options]
691
- ```
692
-
693
- **Options**
694
- `--profile` _(string)_
695
- Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
696
-
697
- `--mon_num` _(number)_
698
- Specifies the unique monitor number of the measurement.
699
-
700
- `--module` _(string)_
701
- Specifies the module name that you request the Histogram data for. You get the module value from the 'codeview csect' or from the 'codeview module' command response. The module name can be empty (e.g., --module "IGZCPAC" or --module '""').
702
-
703
- `--csect` _(string)_
704
- Specifies the CSECT name that you request the Histogram data for. You get the csect value from the 'codeview csect' command response. The CSECT name can be empty (e.g., --csect "TUNCOB01" or --module '""').
705
-
706
- `--top` _(number)_
707
- Specifies the maximum number of the top consuming CSECT activity locations that you want to obtain in the response (e.g., --top 5). If you specify --top 0, you get the list of all CSECT activity locations that MAT has detected during the measurement. The --top parameter is optional. Values: numbers between 0 and 300.
708
-
709
- `--group` _(number)_
710
- Specifies the histogram group size parameter that defines the resolution of the histogram. If you do not specify the group parameter, the group size defaults to 4 bytes (e.g., --group 32). If program listing is registered with MAT, the group parameter is ignored. The --group parameter is optional.
711
-
712
- `--listing` _(boolean)_
713
- Enables you to retrieve program listing details that pertain to the specific CSECT and statement. To use the listing retrieval option, you must install and configure the Endevor® Web Services and have the program listing for the specific measurement registered with MAT. The source code listing is retrieved through Endevor® footprints for Cobol, C/C++, and Assembler programs. The program listing file is downloaded to your local directory that you specified with the 'listingDir' parameter for your MAT configuration profile. When you request the histogram details with the '--listing' option, the 'histogram' command returns the additional 'listing' column that contains a reference to the program listing with the specific CSECT name, program type, line and column number that pertain to the requested CSECT and statement, for example, c:\listings\SA420LE.asm:382:51. If you use Visual Studio Code (VS Code) IDE, you can click on the reference in the command response in your VS Code terminal to navigate directly to the indicated source program location. The --listing parameter is optional.
714
-
715
- **Examples**
716
-
717
- - Get the Histogram details with the group size defaulting to 4 bytes for monitor number 5, CSECT name TUNCOB01, module name RUNCOB:
718
-
719
- ```
720
- $ zowe mat monitor codeview histogram --mon_num 5 --csect "TUNCOB01" --module "RUNCOB"
721
- ```
722
-
723
- - Get the Histogram details for the latest monitor in the TESTPROF profile for CSECT name TUNCOB01, empty module name, with the group size value set to 32 bytes, and limit the number of returned rows to 5 top consumers:
724
-
725
- ```
726
- $ zowe mat monitor codeview histogram --profile TESTPROF --csect "TUNCOB01" --module '""' --top 5 --group 32
727
- ```
728
-
729
- - Get the Histogram details for monitor number 5, CSECT name TUNCOB01, and module name RUNCOB, limit the number of returned records to 5 top consumers, and request the listing details:
730
-
731
- ```
732
- $ zowe mat monitor codeview histogram --mon_num 5 --csect "TUNCOB01" --module "RUNCOB" --top 5 --listing
733
- ```
734
-
735
- - Get the Histogram details with the group size defaulting to 4 bytes for monitor number 5, CSECT name TUNCOB01, module name RUNCOB, with the specific MAT profile details defined:
736
-
737
- ```
738
- $ zowe mat monitor codeview histogram --mon_num 5 --csect "TUNCOB01" --module "RUNCOB" --host "example.com" --port 12345 --user johndoe --password qwerty
739
- ```
740
-
741
- #### callerid | cil
742
-
743
- Get the CodeView CallerID details for the specific CSECT and module.
744
-
745
- **Usage**
746
-
747
- ```
748
- $ zowe mat monitor codeview callerid [options]
749
- ```
750
-
751
- **Options**
752
- `--profile` _(string)_
753
- Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
754
-
755
- `--mon_num` _(number)_
756
- Specifies the unique monitor number of the measurement.
757
-
758
- `--module` _(string)_
759
- Specifies the module name that you request the CallerID details for. You get the module value from the 'codeview csect' or from the 'codeview module' command response. The module name can be empty (e.g., --module "IGZCPAC" or --module '""').
760
-
761
- `--csect` _(string)_
762
- Specifies the CSECT name that you request the CallerID details data for. You get the csect value from the 'codeview csect' command response. The CSECT name can be empty (e.g., --csect "TUNCOB01" or --csect '""').
763
-
764
- **Examples**
765
-
766
- - Get the CallerID details for monitor number 5, CSECT name TUNCOB01, and module name RUNCOB:
767
-
768
- ```
769
- $ zowe mat monitor codeview callerid --mon_num 5 --csect "TUNCOB01" --module "RUNCOB"
770
- ```
771
-
772
- - Get the CallerID details for the latest monitor in the profile for CSECT name TUNCOB01, and empty module name:
773
-
774
- ```
775
- $ zowe mat monitor codeview callerid --profile TESTPROF --csect "TUNCOB01" --module '""'
776
- ```
777
-
778
- - Get the CallerID details for monitor number 5, CSECT name TUNCOB01, and module name RUNCOB, with the specific MAT profile details defined:
779
-
780
- ```
781
- $ zowe mat monitor codeview callerid --mon_num 5 --csect "TUNCOB01" --module "RUNCOB" --host "example.com" --port 12345 --user johndoe --password qwerty
782
- ```
783
-
784
- ### db2
785
-
786
- The commands from the DB2 group enable you to get the DB2 measurement details.
787
-
788
- **Usage**
789
-
790
- ```
791
- $ zowe mat monitor db2 <command>
792
- ```
793
-
794
- The following **commands** are available for the DB2 group:
795
-
796
- #### db2view | db2
797
-
798
- Get the DB2View details for the measurement.
799
-
800
- **Usage**
801
-
802
- ```
803
- $ zowe mat monitor db2 db2view [options]
804
- ```
805
-
806
- **Options**
807
- `--profile` _(string)_
808
- Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
809
-
810
- `--mon_num` _(number)_
811
- Specifies the unique monitor number of the measurement.
812
-
813
- `--top` _(number)_
814
- Specifies the maximum number of the top consuming DB2 statements that you want to obtain in the response (e.g., --top 5). If you specify --top 0, you get the list of of all DB2 statements that MAT has detected during the measurement. The --top parameter is optional. Values: numbers between 0 and 300.
815
-
816
-
817
- **Examples**
818
-
819
- - Get the DB2View details for monitor number 5:
820
-
821
- ```
822
- $ zowe mat monitor db2 db2view --mon_num 5
823
- ```
824
-
825
- - Get the DB2View details for the latest monitor in the profile, with the top consumer limitation set to 5 top consumers:
826
-
827
- ```
828
- $ zowe mat monitor db2 db2view --profile TESTPROF --top 5
829
- ```
830
-
831
- - Get the DB2View details for monitor number 5, with the specific MAT profile details defined:
832
-
833
- ```
834
- $ zowe mat monitor db2 db2view --mon_num 5 --host "example.com" --port 12345 --user johndoe --password qwerty
835
- ```
836
-
837
- #### sqlstmt | sql
838
-
839
- Get SQL details for the DB2 statement.
840
-
841
- **Usage**
842
-
843
- ```
844
- $ zowe mat monitor db2 sqlstmt [options]
845
- ```
846
-
847
- **Options**
848
- `--profile` _(string)_
849
- Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
850
-
851
- `--mon_num` _(number)_
852
- Specifies the unique monitor number of the measurement.
853
-
854
- `--dbrm` _(string)_
855
- Specifies the DBRM/Package name that the requested DB2 statement belongs to (e.g., `--dbrm CUPBTSDY`). You get the dbrm value from the 'db2 db2view' command response.
856
-
857
- `--stmtnum` _(number)_
858
- Specifies the statement number that you request the SQL details for (e.g., `--stmtnum 464`). You get the stmtnum value from the 'db2 db2view' command response.
859
-
860
- `--totalsamps` _(number)_
861
- Specifies the total number of samples taken for the requested statement (e.g., `--totalsamps 1`). You get the totalsamps value from the 'db2 db2view' command response.
862
-
863
- **Examples**
864
-
865
- - Get the DB2 SQL statement details for monitor number 5 for DBRM CUPBTSDY, statement number 464, with total number of taken samples 1:
866
-
867
- ```
868
- $ zowe mat monitor db2 sqlstmt --mon_num 5 --dbrm CUPBTSDY --stmtnum 464 --totalsamps 1
869
- ```
870
-
871
- - Get the DB2 SQL statement details for the latest monitor in the profile, for DBRM CUPBTSDY, statement number 464, with total number of taken samples 1:
872
-
873
- ```
874
- $ zowe mat monitor db2 sqlstmt --profile TESTPROF --dbrm CUPBTSDY --stmtnum 464 --totalsamps 1
875
- ```
876
-
877
- - Get the DB2 SQL statement details for monitor number 5 for DBRM CUPBTSDY, statement number 464, with total number of taken samples 1, with the specific MAT profile details defined:
878
-
879
- ```
880
- $ zowe mat monitor db2 sqlstmt --mon_num 5 --dbrm CUPBTSDY --stmtnum 464 --totalsamps 1 --host "example.com" --port 12345 --user johndoe --password qwerty
881
- ```
882
-
883
- ### idms
884
-
885
- The commands from the idms group enable you to get the IDMS measurement details in DML mode.
886
-
887
- **Usage**
888
-
889
- ```
890
- $ zowe mat monitor idms <command>
891
- ```
892
-
893
- The following **commands** are available for the IDMS group:
894
-
895
- #### dml | dml
896
-
897
- Get the IDMS measurement details in DML mode.
898
-
899
- **Usage**
900
-
901
- ```
902
- $ zowe mat monitor idms dml [options]
903
- ```
904
-
905
- **Options**
906
- `--profile` _(string)_
907
- Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
908
-
909
- `--mon_num` _(number)_
910
- Specifies the unique monitor number of the measurement.
911
-
912
- **Examples**
913
-
914
- - Get the dml measurement details for the latest monitor in the TESTPROF profile:
915
-
916
- ```
917
- $ zowe mat monitor idms dml --profile TESTPROF
918
- ```
919
-
920
- - Get the dml details of the measurement for monitor number 5:
921
-
922
- ```
923
- $ zowe mat monitor idms dml --mon_num 5
924
- ```
925
-
926
- #### module | mod
927
-
928
- Get the IDMS measurement details.
929
-
930
- **Usage**
931
-
932
- ```
933
- $ zowe mat monitor idms module [options]
934
- ```
935
-
936
- **Options**
937
- `--profile` _(string)_
938
- Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
939
-
940
- `--mon_num` _(number)_
941
- Specifies the unique monitor number of the measurement.
942
-
943
- `--module` _(string)_
944
- Specifies the module name that you request the details for. The module name can be empty (e.g., --module "IGZCPAC" or --module '""').
945
-
946
- `--taskid` _(number)_
947
- Specifies the identifier of the Task that you request the details for.
948
-
949
- `--ruid` _(number)_
950
- Specifies the identifier of the Run Unit that you request the details for.
951
-
952
- `--linecmd` _(string)_
953
- Specifies the line command to be used for the row data.
954
-
955
- **Examples**
956
-
957
- - Get the idms details of the measurement for the latest monitor in the profile:
958
-
959
- ```
960
- $ zowe mat monitor idms module --profile TESTPROF
961
- ```
962
-
963
- - Get the module details of the measurement for monitor number 5:
964
-
965
- ```
966
- $ zowe mat monitor idms module --mon_num 5
967
- ```
968
-
969
- - Specify the module taskid, ruid, and linecmd option of the measurement for the module mode for the TESTPROF profile:
970
-
971
- ```
972
- $ zowe mat monitor idms module --profile TESTPROF --module SQLA01D --taskid 1 --ruid 33333 --linecmd dispatch
973
- ```
974
-
975
- #### task | ts
976
-
977
- Get the IDMS measurement details in Task mode.
978
-
979
- **Usage**
980
-
981
- ```
982
- $ zowe mat monitor idms task [options]
983
- ```
984
-
985
- **Options**
986
- `--profile` _(string)_
987
- Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
988
-
989
- `--mon_num` _(number)_
990
- Specifies the unique monitor number of the measurement.
991
-
992
- **Examples**
993
-
994
- Get the idms measurement details in Task mode for monitor number 5:
995
-
996
- ```
997
- $ zowe mat monitor idms task --mon_num 5
998
- ```
999
-
1000
- Get the idms measurement details in Task mode for the latest monitor in the profile:
1001
-
1002
- ```
1003
- $ zowe mat monitor idms task --profile TESTPROF
1004
- ```
1005
-
1006
- ### ims
1007
-
1008
- The commands from the ims group enable you to get the IMS measurement details.
1009
-
1010
- **Usage**
1011
-
1012
- ```
1013
- $ zowe mat monitor ims <command>
1014
- ```
1015
-
1016
- The following **commands** are available for the IMS group:
1017
-
1018
- #### imsview | imsv
1019
-
1020
- Get the IMS View details for the measurement.
1021
-
1022
- **Usage**
1023
-
1024
- ```
1025
- $ zowe mat monitor ims imsview [options]
1026
- ```
1027
-
1028
- **Options**
1029
- `--profile` _(string)_
1030
- Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
1031
-
1032
- `--mon_num` _(number)_
1033
- Specifies the unique monitor number of the measurement.
1034
-
1035
- **Examples**
1036
-
1037
- - Get the IMS View details for monitor number 5:
1038
-
1039
- ```
1040
- $ zowe mat monitor ims imsview --mon_num 5
1041
- ```
1042
-
1043
- - Get the IMS View details for the latest monitor in the profile:
1044
-
1045
- ```
1046
- $ zowe mat monitor ims imsview --profile TESTPROF
1047
- ```
1048
-
1049
- #### dbdname | dbd
1050
-
1051
- Get the IMS View DBDName data.
1052
-
1053
- **Usage**
1054
-
1055
- ```
1056
- $ zowe mat monitor ims dbdname [options]
1057
- ```
1058
-
1059
- **Options**
1060
- `--profile` _(string)_
1061
- Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
1062
-
1063
- `--mon_num` _(number)_
1064
- Specifies the unique monitor number of the measurement.
1065
-
1066
- **Examples**
1067
-
1068
- - Get the IMS View DBDName details for monitor number 5:
1069
-
1070
- ```
1071
- $ zowe mat monitor ims dbdname --mon_num 5
1072
- ```
1073
-
1074
- - Get the IMS View DBDName details for the latest monitor in the profile:
1075
-
1076
- ```
1077
- $ zowe mat monitor ims dbdname --profile TESTPROF
1078
- ```
1079
-
1080
- #### psbname | psb
1081
-
1082
- Get the IMS View PSBName measurement details.
1083
-
1084
- **Usage**
1085
-
1086
- ```
1087
- $ zowe mat monitor ims psbname [options]
1088
- ```
1089
-
1090
- **Options**
1091
- `--profile` _(string)_
1092
- Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
1093
-
1094
- `--mon_num` _(number)_
1095
- Specifies the unique monitor number of the measurement.
1096
-
1097
- **Examples**
1098
-
1099
- - Get the IMS View PSBName details for monitor number 5:
1100
-
1101
- ```
1102
- $ zowe mat monitor ims psbname --mon_num 5
1103
- ```
1104
-
1105
- - Get the IMS View PSBName details for the latest monitor in the profile:
1106
-
1107
- ```
1108
- $ zowe mat monitor ims psbname --profile TESTPROF
1109
- ```
1110
-
1111
- #### region | reg
1112
-
1113
- Get the IMS View Region measurement details.
1114
-
1115
- **Usage**
1116
-
1117
- ```
1118
- $ zowe mat monitor ims region [options]
1119
- ```
1120
-
1121
- **Options**
1122
- `--profile` _(string)_
1123
- Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
1124
-
1125
- `--mon_num` _(number)_
1126
- Specifies the unique monitor number of the measurement.
1127
-
1128
- **Examples**
1129
-
1130
- - Get the IMS View Region details for monitor number 5:
1131
-
1132
- ```
1133
- $ zowe mat monitor ims region --mon_num 5
1134
- ```
1135
-
1136
- - Get the IMS View Region details for the latest monitor in the profile:
1137
-
1138
- ```
1139
- $ zowe mat monitor ims region --profile TESTPROF
1140
- ```
1141
-
1142
- #### ssa | ssa
1143
-
1144
- Get the IMS View Region measurement details.
1145
-
1146
- **Usage**
1147
-
1148
- ```
1149
- $ zowe mat monitor ims ssa [options]
1150
- ```
1151
-
1152
- **Options**
1153
- `--profile` _(string)_
1154
- Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
1155
-
1156
- `--mon_num` _(number)_
1157
- Specifies the unique monitor number of the measurement.
1158
-
1159
- `--call` _(string)_
1160
- Specifies the call details for the specified monitor number or profile name.
1161
-
1162
- `--dbdname` _(string)_
1163
- Specifies the database details for the specified monitor number or profile name.
1164
-
1165
- `--psbname` _(string)_
1166
- Specifies the PSB name details for the specified monitor number or profile name.
1167
-
1168
- **Examples**
1169
-
1170
- - Get the IMS View SSA details for monitor number 5 with the specific MAT profile details defined:
1171
-
1172
- ```
1173
- $ zowe mat monitor ims ssa --mon_num 5 --call TESTCALL --dbdname TESTDBDNAME --psbname TESTPSBNAME
1174
- ```
1175
-
1176
- - Get the IMS View SSA details for the latest monitor in the TESTPROF profile with the specific MAT profile details defined:
1177
-
1178
- ```
1179
- $ zowe mat monitor ims ssa --profile TESTPROF --call TESTCALL --dbdname TESTDBDNAME --psbname TESTPSBNAME
1180
- ```
1181
-
1182
- #### statement | stat
1183
-
1184
- Get the IMS View Statement measurement details.
1185
-
1186
- **Usage**
1187
-
1188
- ```
1189
- $ zowe mat monitor ims statement [options]
1190
- ```
1191
-
1192
- **Options**
1193
- `--profile` _(string)_
1194
- Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
1195
-
1196
- `--mon_num` _(number)_
1197
- Specifies the unique monitor number of the measurement.
1198
-
1199
- `--trancode` _(string)_
1200
- Specifies the transaction name for specified monitor number or profile name.
1201
-
1202
- **Examples**
1203
-
1204
- - Get the IMS View Statement details for monitor number 5 with trancode:
1205
-
1206
- ```
1207
- $ zowe mat monitor ims statement --mon_num 5 --trancode TESTTRANCODE
1208
- ```
1209
-
1210
- - Get the IMS View Statement details for the latest monitor in the profile with trancode:
1211
-
1212
- ```
1213
- $ zowe mat monitor ims statement --profile TESTPROF --trancode TESTTRANCODE
1214
- ```
1215
-
1216
- ### tranview
1217
-
1218
- The commands from the tranview group enable you to get the TranView measurement details.
1219
-
1220
- **Usage**
1221
-
1222
- ```
1223
- $ zowe mat monitor tranview <command>
1224
- ```
1225
-
1226
- The following **commands** are available for the TranView group:
1227
-
1228
- #### all | all
1229
-
1230
- Get the TranView measurement details in Module mode.
1231
-
1232
- **Usage**
1233
-
1234
- ```
1235
- $ zowe mat monitor tranview all [options]
1236
- ```
1237
-
1238
- **Options**
1239
- `--profile` _(string)_
1240
- Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
1241
-
1242
- `--mon_num` _(number)_
1243
- Specifies the unique monitor number of the measurement.
1244
-
1245
- `--tran` _(string)_
1246
- Specifies the transaction activity. Tran = N/A is displayed for the activity that could not be attributed to a particular transaction in the address space.
1247
-
1248
- **Examples**
1249
-
1250
- - Get the TranView measurement details for monitor number 5:
1251
-
1252
- ```
1253
- $ zowe mat monitor tranview all --mon_num 5
1254
- ```
1255
-
1256
- - Get the TranView measurement details for the latest monitor in the TESTPROF profile:
1257
-
1258
- ```
1259
- $ zowe mat monitor tranview all --profile TESTPROF
1260
- ```
1261
-
1262
- #### module | mod
1263
-
1264
- Get the TranView measurement details.
1265
-
1266
- **Usage**
1267
-
1268
- ```
1269
- $ zowe mat monitor tranview module [options]
1270
- ```
1271
-
1272
- **Options**
1273
- `--profile` _(string)_
1274
- Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
1275
-
1276
- `--mon_num` _(number)_
1277
- Specifies the unique monitor number of the measurement.
1278
-
1279
- `--tran` _(string)_
1280
- Specifies the transaction activity. Tran = N/A is displayed for the activity that could not be attributed to a particular transaction in the address space.
1281
-
1282
- **Examples**
1283
-
1284
- - Get the idms details of the measurement for the latest monitor in the profile:
1285
-
1286
- ```
1287
- $ zowe mat monitor tranview module --profile TESTPROF
1288
- ```
1289
-
1290
- - Get the module details of the measurement for monitor number 5:
1291
-
1292
- ```
1293
- $ zowe mat monitor tranview module --mon_num 5
1294
- ```
1295
-
1296
- - Specify the module taskid, ruid, and linecmd option of the measurement for the module mode for the TESTPROF profile:
1297
-
1298
- ```
1299
- $ zowe mat monitor tranview module --tran MVGT
1300
- ```
1301
-
1302
- #### callerid | cid
1303
-
1304
- Get the caller identifier details.
1305
-
1306
- **Usage**
1307
-
1308
- ```
1309
- $ zowe mat monitor tranview callerid [options]
1310
- ```
1311
-
1312
- **Options**
1313
- `--profile` _(string)_
1314
- Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
1315
-
1316
- `--mon_num` _(number)_
1317
- Specifies the unique monitor number of the measurement.
1318
-
1319
- `--tran` _(string)_
1320
- Specifies the transaction activity. Tran = N/A is displayed for the activity that could not be attributed to a particular transaction in the address space.
1321
-
1322
- **Examples**
1323
-
1324
- - Get the caller details for monitor number 5:
1325
-
1326
- ```
1327
- $ zowe mat monitor tranview callerid --mon_num 5
1328
- ```
1329
-
1330
- - Get the caller details for the latest monitor in the TESTPROF profile:
1331
-
1332
- ```
1333
- $ zowe mat monitor tranview callerid --profile TESTPROF
1334
- ```
1335
-
1336
- #### callstack | csk
1337
-
1338
- Get CallStack data in Module mode.
1339
-
1340
- **Usage**
1341
-
1342
- ```
1343
- $ zowe mat monitor tranview callstack [options]
1344
- ```
1345
-
1346
- **Options**
1347
- `--profile` _(string)_
1348
- Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
1349
-
1350
- `--mon_num` _(number)_
1351
- Specifies the unique monitor number of the measurement.
1352
-
1353
- `--tran` _(string)_
1354
- Specifies the transaction activity. Tran = N/A is displayed for the activity that could not be attributed to a particular transaction in the address space.
1355
-
1356
- **Examples**
1357
-
1358
- - Get the callstack details for monitor number 5:
1359
-
1360
- ```
1361
- $ zowe mat monitor tranview callstack --mon_num 5
1362
- ```
1363
-
1364
- - Get the callstack details for the latest monitor in the TESTPROF profile:
1365
-
1366
- ```
1367
- $ zowe mat monitor tranview callstack --profile TESTPROF
1368
- ```
1369
-
1370
- #### csect | csd
1371
-
1372
- Get the CodeView details for transaction in Csect mode.
1373
-
1374
- **Usage**
1375
-
1376
- ```
1377
- $ zowe mat monitor tranview csect [options]
1378
- ```
1379
-
1380
- **Options**
1381
- `--profile` _(string)_
1382
- Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
1383
-
1384
- `--mon_num` _(number)_
1385
- Specifies the unique monitor number of the measurement.
1386
-
1387
- `--tran` _(string)_
1388
- Specifies the transaction activity. Tran = N/A is displayed for the activity that could not be attributed to a particular transaction in the address space.
1389
-
1390
- **Examples**
1391
-
1392
- - Get the CodeView details for transaction in Csect mode for monitor number 5:
1393
-
1394
- ```
1395
- $ zowe mat monitor tranview csect --mon_num 5
1396
- ```
1397
-
1398
- - Get the CodeView details for transaction in Csect mode for the latest monitor in the TESTPROF profile:
1399
-
1400
- ```
1401
- $ zowe mat monitor tranview csect --profile TESTPROF
1402
- ```
1403
-
1404
- - Get the CodeView details for transaction in Csect mode for the monitor number 5 with specific host:
1405
-
1406
- ```
1407
- $ zowe mat monitor tranview csect --mon_num 5 --host \"example.com\" --port 12345 --user User1 --password qwerty
1408
- ```
1409
-
1410
- #### delay | dl
1411
-
1412
- Get the delay details for the measurement.
1413
-
1414
- **Usage**
1415
-
1416
- ```
1417
- $ zowe mat monitor tranview delay [options]
1418
- ```
1419
-
1420
- **Options**
1421
- `--profile` _(string)_
1422
- Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
1423
-
1424
- `--mon_num` _(number)_
1425
- Specifies the unique monitor number of the measurement.
1426
-
1427
- `--tran` _(string)_
1428
- Specifies the transaction activity. Tran = N/A is displayed for the activity that could not be attributed to a particular transaction in the address space.
1429
-
1430
- **Examples**
1431
-
1432
- - Get the DelayView measurement details of a transaction for monitor number 5:
1433
-
1434
- ```
1435
- $ zowe mat monitor tranview delay --mon_num 5
1436
- ```
1437
-
1438
- - Get the DelayView measurement details for the latest monitor in the TESTPROF profile:
1439
-
1440
- ```
1441
- $ zowe mat monitor tranview delay --profile TESTPROF
1442
- ```
1443
-
1444
- - Get the DelayView measurement details for monitor number 5, with the specific MAT profile details defined:
1445
-
1446
- ```
1447
- $ zowe mat monitor tranview delay --mon_num 5 --host \"example.com\" --port 12345 --user User1 --password qwerty
1448
- ```
1449
-
1450
- #### stat | cis
1451
-
1452
- Get the CICS statistics details.
1453
-
1454
- **Usage**
1455
-
1456
- ```
1457
- $ zowe mat monitor tranview stat [options]
1458
- ```
1459
-
1460
- **Options**
1461
- `--profile` _(string)_
1462
- Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
1463
-
1464
- `--mon_num` _(number)_
1465
- Specifies the unique monitor number of the measurement.
1466
-
1467
- `--tran` _(string)_
1468
- Specifies the transaction activity. Tran = N/A is displayed for the activity that could not be attributed to a particular transaction in the address space.
1469
-
1470
- `--type` _(string)_
1471
- Specifies the type of CICS Transaction.
1472
- Default value: DISP
1473
-
1474
- **Examples**
1475
-
1476
- - Get the CICS statistic details for monitor number 5:
1477
-
1478
- ```
1479
- $ zowe mat monitor tranview stat --mon_num 5 --type DB
1480
- ```
1481
-
1482
- - Get the CICS statistics details for the latest monitor in the TESTPROF profile:
1483
-
1484
- ```
1485
- $ zowe mat monitor tranview stat --profile TESTPROF
1486
- ```
1487
-
1488
- # Uninstall the MAT Analyze Plug-in for Zowe CLI
1489
-
1490
- To uninstall the MAT Analyze plug-in for Zowe CLI, issue the following command:
1491
-
1492
- ```
1493
- $ zowe plugins uninstall @broadcom/mat-analyze-for-zowe-cli
1494
- ```
1
+ <img src="https://artwork.openmainframeproject.org/other/zowe-conformant/zowev2/cli/color/zowe-conformant-zowev2-cli-color.png" width="100" height="75" alt="Zowe Conformance Badge">
2
+
3
+ # MAT Analyze Plug-in for Zowe CLI
4
+
5
+ The MAT Analyze plug-in for Zowe CLI provides access to Mainframe Application Tuner (MAT) functionality. The plug-in ensures interaction with MAT and enables you to measure your mainframe applications and get the analysis data in the form of MAT analysis views using Zowe command line interface.
6
+
7
+ You can use the MAT Analyze plug-in for Zowe CLI to perform the following tasks:
8
+
9
+ - Manage monitor profiles.
10
+ Create and invoke monitor profiles, view the lists of available profiles, and retrieve the measurement history.
11
+ - Analyze the measurement data.
12
+ Access the measurement data from Mainframe Application Tuner that is available to you in the CLI in the form of MAT analysis views.
13
+ - Address performance issues.
14
+ With the source program listing registered with MAT, users of Visual Studio Code (VS Code) IDE can obtain the Histogram details and display specific source program locations that are associated with the most resource-consuming program modules and CSECTs. When you request the Histogram measurement details from your VS Code command line terminal, the MAT Analyze plug-in for Zowe CLI transfers the source code listing to your local machine and navigates you directly to the specific line and column number of the source code, which enables you to immediately inspect the program statement and identify possible tuning opportunities.
15
+
16
+ # Table of Contents
17
+
18
+ - [Installation](#installation)
19
+ - [Prerequisites](#prerequisites)
20
+ - [Install the MAT Analyze Plug-in for Zowe CLI From Packages](#install-the-mat-analyze-plug-in-for-zowe-cli-from-packages)
21
+ - [Validate the Installation](#validate-the-installation)
22
+ - [Create a MAT Profile](#create-a-mat-profile)
23
+ - [Use MAT Profile Options](#use-mat-profile-options)
24
+ - [Use Cases and Commands](#use-cases-and-commands)
25
+ - [PROFILE](#profile)
26
+ - [create | cr](#create--cr)
27
+ - [invoke | ivk](#invoke--ivk)
28
+ - [list | lip](#list--lip)
29
+ - [MONITOR](#monitor)
30
+ - [history | hs](#history--hs)
31
+ - [overview | ov](#overview--ov)
32
+ - [delayview](#delayview)
33
+ - [delay | de](#delay--de)
34
+ - [address | ad](#address--ad)
35
+ - [codeview](#codeview)
36
+ - [module | mod](module--mod)
37
+ - [csect | cs](#csect--cs)
38
+ - [histogram | hsg](#histogram--hsg)
39
+ - [callerid | cil](#callerid--cil)
40
+ - [db2](#db2)
41
+ - [db2view | db2](#db2view--db2)
42
+ - [sqlstmt | sql](#sqlstmt--sql)
43
+ - [idms](#idms)
44
+ - [dml | dml](#dml--dml)
45
+ - [module | mod](#idms)
46
+ - [task | ts](#task--ts)
47
+ - [ims](#ims)
48
+ - [dbdname | dbd](#dbdname--dbd)
49
+ - [imsview | imsv](#imsview--imsv)
50
+ - [psbname | psb](#psbname--psb)
51
+ - [region | reg](#region--reg)
52
+ - [ssa | ssa](#ssa--ssa)
53
+ - [statement | stat](#statement--stat)
54
+ - [tranview](#tranview)
55
+ - [all | all](#all--all)
56
+ - [module | mod](#tranview)
57
+ - [callerid | cid](#callerid--cid)
58
+ - [callstack | csk](#callstack--csk)
59
+ - [csect | csd](#csect--csd)
60
+ - [delay | dl](#delay--dl)
61
+ - [stat | cis](#stat--cis)
62
+ - [Uninstall the MAT Analyze Plug-in for Zowe CLI](#uninstall-the-mat-analyze-plug-in-for-zowe-cli)
63
+
64
+ # Installation
65
+
66
+ You can install the MAT Analyze Plug-in for Zowe CLI from the Zowe Package.
67
+
68
+ ## Prerequisites
69
+
70
+ Before starting the installation of the MAT Analyze Plug-in for Zowe CLI, verify that you have:
71
+
72
+ - Zowe version 2 (Zowe CLI version 7.x) is installed.
73
+ - MAT database and the REST API installed, configured, and running.
74
+ - (Optional) To use the automated listing registration and retrieval option through Endevor® footprints, install and configure the Endevor® Web Services and specify the Endevor® web server details in the MAT database configuration.
75
+
76
+ ## Install the MAT Analyze Plug-in for Zowe CLI From Packages
77
+
78
+ Issue the following command:
79
+
80
+ ```
81
+ $ zowe plugins install @broadcom/mat-analyze-for-zowe-cli
82
+ ```
83
+
84
+ **Note:**
85
+ The `latest` npm tag installs a version of the product that is intended for public consumption. You can use different npm tags to install other versions of the product. For example, you can install with the `@beta` tag to try new features that have not been fully validated. For more information about tag usage, see [NPM Tag Names](https://github.com/zowe/zowe-cli/blob/master/docs/MaintainerVersioning.md#npm-tag-names).
86
+
87
+ ## Validate the Installation
88
+
89
+ To validate the installation, issue the following command:
90
+
91
+ ```
92
+ $ zowe plugins validate @broadcom/mat-analyze-for-zowe-cli
93
+ ```
94
+
95
+ Successful validation of the plug-in returns the response "This plugin was successfully validated. Enjoy the plugin."
96
+
97
+ ## Create a MAT Profile
98
+
99
+ To enable the interaction of the MAT Analyze plug-in for Zowe CLI with MAT, you need to specify the MAT profile details that include the protocol type, host, and port that you defined for the MAT REST API server, and your mainframe username and password. The details of the MAT profile are stored in the Zowe configuration file. To create a global Zowe configuration file, use the command `zowe config init --global-config`, then edit the configuration file and add a section with the MAT profile details:
100
+
101
+ ```
102
+ "mat": {
103
+             "type": "mat",
104
+             "properties": {
105
+                 "host": "example.com",
106
+                 "protocol": "http",
107
+                 "port": "12345",
108
+                 "user": "johndoe",
109
+                 "password": "qwerty",
110
+                 "listingDir": "c:\listings",
111
+                 "rejectUnauthorized": false
112
+             },
113
+             "secure": []
114
+         },
115
+ ```
116
+
117
+ ## Use MAT Profile Options
118
+
119
+ `--protocol` | `--o` _(string)_
120
+ Specifies the protocol defined for the MAT REST API server (http or https).
121
+ Allowed values: http, https.
122
+
123
+ `--host` | `--H` _(string)_
124
+ Specifies the hostname or IP address defined for the MAT REST API server (e.g. 127.0.0.0 or localhost).
125
+
126
+ `--port` | `--P` _(number)_
127
+ Specifies the server port (e.g. 8080).
128
+
129
+ `--user` | `--u` _(string)_
130
+ Your mainframe username.
131
+
132
+ `--password` | `--pw` _(string)_
133
+ Your mainframe password.
134
+
135
+ `--base-path` | `--bp` _(string)_
136
+ The base path for your API mediation layer instance. Specify this option to prepend the base path to all resources when making REST requests. Do not specify this option if you are not using an API mediation layer.
137
+
138
+ `--reject-unauthorized` | `--ru` _(boolean)_
139
+ Reject self-signed certificates.
140
+ Default value: true
141
+
142
+ `--listingDir` | `--ldir` _(string)_
143
+ Specifies the directory where you want to store the registered program listings (e.g. 'c:\listings') for your immediate source code inspection. You can use the advantage of automated listing registration with MAT and listing retrieval through Endevor® footprints for Cobol, C/C++, and Assembler programs. When a source program listing is registered with MAT, you can enhance the histogram analysis data with the program listing details that pertain to the specific CSECT and program statement. The listing is transfered to the specified directory, which enables you to navigate directly to the line of the source code in you VS Code IDE and inspect the program statement. To use the listing retrieval option through Endevor® footprints, you need to have the Endevor® Web Services installed and configured and specify the Endevor® web server details in the MAT database configuration. The `--listingDir` parameter is optional.
144
+
145
+ If the details are not specified or if you want to temporarily use different MAT profile settings, you can specify all or some MAT profile details with each command. The MAT profile details that are provided with a command have the highest priority and override all other values. For more information about using profiles in Zowe, see [Using Global Profile Configuration](https://docs.zowe.org/stable/user-guide/cli-using-global-profile-configuration/) in the Zowe documentation.
146
+
147
+ # Use Cases and Commands
148
+
149
+ The MAT Analyze plug-in for Zowe CLI enables you to manage monitor profiles and get the measurement analysis data using Mainframe Application Tuner (MAT).
150
+
151
+ ```
152
+ $ zowe mat <group>
153
+ ```
154
+
155
+ The MAT Analyze plug-in for Zowe CLI commands are organized in the following **command groups**:
156
+
157
+ ## PROFILE
158
+
159
+ The commands from the PROFILE group enable you to create, invoke, and list MAT monitor profiles.
160
+
161
+ **Usage**
162
+
163
+ ```
164
+ $ zowe mat profile <command>
165
+ ```
166
+
167
+ The following **commands** are available for the PROFILE group:
168
+
169
+ ### create | cr
170
+
171
+ Create a MAT monitor profile.
172
+
173
+ **Usage**
174
+
175
+ ```
176
+ $ zowe mat profile create [options]
177
+ ```
178
+
179
+ **Required Options**
180
+ `--profile` _(string)_
181
+ Specifies the name of the profile that you create in MAT (e.g. PROFILE1).
182
+ Values: 1 to 8 characters, a combination of alphanumeric and national characters (A-Z, 0-9, and @), the first character must be an alphabetic or @. The profile name must not contain characters # and $.
183
+
184
+ `--jobname` _(string)_
185
+ Specifies the name of the job that you want to measure (e.g. JOB1).
186
+ Values: 1 to 8 characters, alphanumeric (A-Z capitals only and 0-9), national (#, $, @), and wildcards (\* or %).
187
+
188
+ `--targsys` _(string)_
189
+ Specifies the target system in SYSPLEX.
190
+ Values: a comma separated list of up to 4 values is allowed, 1-8 characters each, a combination of alphanumeric (A-Z and 0-9) and national (@,#,$), the first character must be an alphabetic (A-Z) or a national (@, #, $), e.g. AA31,AA32).
191
+
192
+ **Options**
193
+ `--batchreports` _(string)_
194
+ Specifies the setting for the Batch report option upon monitor completion.
195
+ Default value: no.
196
+ Allowed values: yes, no.
197
+
198
+ `--description` _(string)_
199
+ Provide the monitor description (maximum 24 characters).
200
+
201
+ `--mondsn` _(string)_
202
+ Specifies the monitor data set name where MAT saves the measurement (e.g. DEMO.MAT.MONITOR).
203
+ Values: data set name pattern, maximum 46 characters. If not specified, your default MAT monitor DSN pattern is applied.
204
+
205
+ `--stepname` _(string)_
206
+ Specifies the name of the job step to monitor.
207
+ Values: maximum 8 characters, alphanumeric (A-Z capitals only and 0-9), national (#, $, @), and wildcards (\* or %).
208
+
209
+ `--mstep` _(string)_
210
+ Indicates whether the multi-step monitoring option is enabled.
211
+ Default value: no.
212
+ Allowed values: yes, no.
213
+
214
+ `--procstep` _(string)_
215
+ Specifies the name of the procedure step.
216
+ Values: maximum 8 characters, alphanumeric (A-Z capitals only and 0-9), national (#, $, @), and wildcards (\* or %).
217
+
218
+ `--program` _(string)_
219
+ Specifies the name of the program to monitor.
220
+ Values: maximum 8 characters, alphanumeric (A-Z capitals only and 0-9), national (#, $, @), and wildcards (\* or %).
221
+
222
+ `--elapstime` _(string)_
223
+ Specifies the required monitor duration followed by s (seconds) or m (minutes) (e.g. 60s).
224
+ Values: maximum 6 characters total, number must be > 0.
225
+ Default value: 60s.
226
+
227
+ `--smon` _(string)_
228
+ Specifies whether to monitor the entire step.
229
+ Default value: no.
230
+ Allowed values: yes, no.
231
+
232
+ `--tasklib` _(string)_
233
+ Specifies an additional DD name for load modules.
234
+ Values: maximum 8 characters, alphanumeric (A-Z capitals only and 0-9), national (#, $, @), and wildcards (\* or %).
235
+
236
+ `--samplecnt` _(string)_
237
+ Specifies the number of observations requested.
238
+ Values: maximum 6 characters, numbers between 10 and 999999.
239
+ Default value: 6000.
240
+
241
+ `--succnt` _(string)_
242
+ Specifies the maximum number of monitors to run per job execution. Values: maximum 4 characters, numbers between 1 and 9999.
243
+ Default value: 1.
244
+
245
+ `--reccnt` _(string)_
246
+ Specifies the number of times this job step will be monitored. Values: maximum 4 characters, numbers between 1 and 9999.
247
+ Default value: 1.
248
+
249
+ `--sampdelay` _(string)_
250
+ Specifies the delay monitoring time in seconds after the step start. Values: maximum 4 characters, numbers between 0 and 9999.
251
+ Default value: 0.
252
+
253
+ `--userexit1` _(string)_
254
+ Specifies the name for the call user written Data Base.
255
+ Values: maximum 8 characters, alphanumeric (A-Z capitals only and 0-9), national (#, $, @), and wildcards (\* or %) (e.g. DBEXIT1).
256
+
257
+ `--userexit2` _(string)_
258
+ Specifies the name 1 for the call user written 4GL exit programs for this monitor.
259
+ Values: maximum 8 characters, alphanumeric (A-Z capitals only and 0-9), national (#, $, @), and wildcards (\* or %) (e.g. UEXIT1).
260
+
261
+ `--userexit3` _(string)_
262
+ Specifies the name 2 for the call user written 4GL exit programs for this monitor.
263
+ Values: maximum 8 characters, alphanumeric (A-Z capitals only and 0-9), national (#, $, @), and wildcards (\* or %) (e.g. UEXIT2).
264
+
265
+ `--inctask` _(string)_
266
+ Specifies the task name to define the tasks that you want to sample in a multitasking environment and restrict monitoring to the specific subtask within the address space.
267
+ Values: a comma separated list of up to 4 values is allowed, maximum 8 characters each, alphanumeric (A-Z capitals only and 0-9), national (#, $, @), and wildcards (\* or %) (e.g. INC31,INC32).
268
+
269
+ `--exctask` _(string)_
270
+ Specifies the task name to omit from sampling in a multitasking environment.
271
+ Values: a comma separated list of up to 4 values is allowed, max. 8 characters each, alphanumeric (A-Z capitals only and 0-9), national (#, $, @), and wildcards (\* or %) (e.g. EXC31,EXC32).
272
+
273
+ `--tran` _(string)_
274
+ Specifies the CICS transaction code name to monitor.
275
+ Values: a comma separated list of up to 4 values is allowed, maximum 8 characters each, alphanumeric (A-Z capitals only and 0-9), national (#, $, @), and wildcards (\* or +) (e.g. TRAN1,TRAN2).
276
+
277
+ `--term` _(string)_
278
+ Specifies the CICS terminal IDs to monitor.
279
+ Values: a comma separated list of up to 4 values is allowed, maximum 8 characters each, alphanumeric (A-Z capitals only and 0-9), national (#, $, @), and wildcards (\* or +) (e.g. TERM1,TERM2).
280
+
281
+ `--userid` _(string)_
282
+ Specifies the CICS user IDs to monitor.
283
+ Values: a comma separated list of up to 4 values is allowed, maximum 8 characters each, alphanumeric (A-Z capitals only and 0-9), national (#, $, @), and wildcards (\* or +) (e.g. USER1,USER2).
284
+
285
+ `--db2expl` _(string)_
286
+ Indicates whether the Explain SQL option is enabled for DB2 SQL statements.
287
+ Default value: no.
288
+ Allowed values: yes, no.
289
+
290
+ `--db2ctsql` _(string)_
291
+ Indicates whether the Collect SQL from Catalog option is enabled for DB2 SQL statements. If you specify db2expl=yes, then db2ctsql must be also set to yes.
292
+ Default value: no.
293
+ Allowed values: yes, no.
294
+
295
+ `--db2hvloc` _(string)_
296
+ Indicates whether the Requestor Location option is enabled for DB2 measurements.
297
+ Default value: no.
298
+ Allowed values: yes, no.
299
+
300
+ `--db2hvcor` _(string)_
301
+ Indicates whether the Correlation ID option for SQL statements is enabled for DB2 measurements.
302
+ Default value: no.
303
+ Allowed values: yes, no.
304
+
305
+ `--db2hviid` _(string)_
306
+ Indicates whether the Operator ID option for SQL statements is enabled for DB2 measurements.
307
+ Default value: no.
308
+ Allowed values: yes, no.
309
+
310
+ `--db2hvthd` _(string)_
311
+ Indicates whether the Thread Address option for SQL statements is enabled for DB2 measurements.
312
+ Default value: no.
313
+ Allowed values: yes, no.
314
+
315
+ `--wasexprt` _(string)_
316
+ Indicates whether the Expert Mode is enabled for Java measurement.
317
+ Default value: no.
318
+ Allowed values: yes, no.
319
+
320
+ `--urlfilt` _(string)_
321
+ A filtering string to restrict monitoring to the specific application URL, transaction, or stored procedure for Java measurements.
322
+ Values: a comma separated list of up to 4 values is allowed, max. 64 characters (e.g. mypage1.html,mypage2.html).
323
+
324
+ `--sysfilt` _(string)_
325
+ A filtering string to include the specified system class for Java measurements. If you specify a value for sysfilt, the measurement includes only the classes that match the filtering string pattern.
326
+ Values: a comma separated list of up to 3 values is allowed, max. 64 characters (e.g. user1.class,user2.class).
327
+
328
+ `--schedule` _(string)_
329
+ Specifies the name of the schedule that you want to apply to the monitor profile (maximum 8 characters).
330
+
331
+ **Examples**
332
+
333
+ - Create the PROFILE1 monitor profile to measure job JOB1 that runs on the AA31 system:
334
+
335
+ ```
336
+ $ zowe mat profile create --profile PROFILE1 --jobname JOB1 --targsys AA31
337
+ ```
338
+
339
+ - Create the PROFILE1 monitor profile to measure for 90 seconds job JOB1 that runs on the AA31 and AA32 systems:
340
+
341
+ ```
342
+ $ zowe mat profile create --profile PROFILE1 --jobname JOB1 --targsys AA31,AA32 --elapstime 90s
343
+ ```
344
+
345
+ - Create the PROFILE1 monitor profile to measure job JOB1 that runs on the AA31 system, with the specific MAT profile details defined:
346
+
347
+ ```
348
+ $ zowe mat profile create --profile PROFILE1 --jobname JOB1 --targsys AA31 --host "example.com" --port 12345 --user johndoe --password qwerty
349
+ ```
350
+
351
+ ### invoke | ivk
352
+
353
+ Invoke a MAT monitor profile to start measurement. If you invoke a monitor profile that does currently exist, MAT creates the profile with the provided name and invokes the measurement for this profile.
354
+
355
+ **Usage**
356
+
357
+ ```
358
+ $ zowe mat profile invoke [options]
359
+ ```
360
+
361
+ **Required Options**
362
+ `--profile` _(string)_
363
+ Specifies the name of the profile in MAT that you invoke (e.g. PROFILE1).
364
+ Values: 1 to 8 characters, a combination of alphanumeric and national characters (A-Z, 0-9, and @), the first character must be an alphabetic or @. The profile name must not contain characters # and $.
365
+
366
+ `--jobname` _(string)_
367
+ Specifies the name of the job to be measured (e.g. JOB1).
368
+ Values: 1 to 8 characters, alphanumeric (A-Z capitals only and 0-9), national (#, $, @), and wildcards (\* or %).
369
+
370
+ `--targsys` _(string)_
371
+ Specifies the target system in SYSPLEX.
372
+ Values: a comma separated list of up to 4 values is allowed, maximum 8 characters each, a combination of alphanumeric (A-Z and 0-9) and national (@,#,$), the first character must be an alphabetic (A-Z) or a national (@, #, $) (e.g. AA31,AA32).
373
+
374
+ **Options**
375
+ `--mondsn` _(string)_
376
+ Specifies the monitor data set name where MAT saves the measurement (e.g. DEMO.MAT.MONITOR).
377
+ Values: data set name pattern, maximum 46 characters. If not specified, your default MAT monitor DSN pattern is applied.
378
+
379
+ `--moiuuid` _(string)_
380
+ Specifies the MOI UUID.
381
+ Values: maximum 61 characters, alphanumeric (A-Z and 0-9). If you use this parameter for command execution, the value cannot be blank.
382
+
383
+ `--moitimestamp` _(string)_
384
+ Specifies the MOI timestamp.
385
+ Values: maximum 12 characters, numbers only (0-9). If you use this parameter for command execution, the value cannot be blank.
386
+
387
+ `--listing` _(boolean)_
388
+ Activates automated registration of Cobol, C/C++, and Assembler program listings through Endevor® footprints. After completion of the measurement that you invoke with the '--listing' parameter, the MAT Analyze plug-in for Zowe CLI automatically retrieves the program listing that is associated with the monitored job and registers the listing with MAT. A registered program listing enhances the analysis possibilities of the 'codeview histogram' command and enables you to inspect the source code statements that are associated with specific modules and CSECTs.
389
+
390
+ **Examples**
391
+
392
+ - Invoke the PROFILE1 monitor profile to measure job JOB1 that runs on the AA31 system:
393
+
394
+ ```
395
+ $ zowe mat profile invoke --profile PROFILE1 --jobname JOB1 --targsys AA31
396
+ ```
397
+
398
+ - Invoke the PROFILE1 monitor profile to measure job JOB1 that runs on the AA31 system and save the measurement result in the DEMO.MAT.MONITOR.PROFILE1 data set:
399
+
400
+ ```
401
+ $ zowe mat profile invoke --profile PROFILE1 --jobname JOB1 --targsys AA31 --mondsn DEMO.MAT.MONITOR.PROFILE1
402
+ ```
403
+
404
+ - Invoke the PROFILE1 monitor profile to measure job JOB1 that runs on the AA31 system and register the program listing:
405
+
406
+ ```
407
+ $ zowe mat profile invoke --profile PROFILE1 --jobname JOB1 --targsys AA31 --listing
408
+ ```
409
+
410
+ - Invoke the PROFILE1 monitor profile to measure job JOB1 that runs on the AA31 system, with the specific MAT profile details defined:
411
+
412
+ ```
413
+ $ zowe mat profile invoke --profile PROFILE1 --jobname JOB1 --targsys AA31 --host "example.com" --port 12345 --user johndoe --password qwerty
414
+ ```
415
+
416
+ ### list | lip
417
+
418
+ Get the list of available monitor profiles.
419
+
420
+ **Usage**
421
+
422
+ ```
423
+ $ zowe mat profile list [options]
424
+ ```
425
+
426
+ ## MONITOR
427
+
428
+ The commands from the MONITOR group enable you to get monitor history and measurement analysis data from MAT.
429
+
430
+ **Usage**
431
+
432
+ ```
433
+ $ zowe mat monitor <command|group>
434
+ ```
435
+
436
+ The following **commands** are available for the MONITOR group:
437
+
438
+ ### history | hs
439
+
440
+ Get the list of all available measurements that are stored in the history of the specific monitor profile.
441
+
442
+ **Usage**
443
+
444
+ ```
445
+ $ zowe mat monitor history [options]
446
+ ```
447
+
448
+ **Options**
449
+ `--profile` _(string)_
450
+ Specifies the name of the profile.
451
+
452
+ **Examples**
453
+
454
+ - Get the list of all available measurements that are stored in the history of the monitor profile TESTPROF:
455
+
456
+ ```
457
+ $ zowe mat monitor history --profile TESTPROF
458
+ ```
459
+
460
+ - Get the list of all available measurements that are stored in the history of the monitor profile TESTPROF, with the specific MAT profile details defined:
461
+
462
+ ```
463
+ $ zowe mat monitor history --profile TESTPROF --host "example.com" --port 12345 --user johndoe --password qwerty
464
+ ```
465
+
466
+ ### overview | ov
467
+
468
+ Get the Overview details of the measurement.
469
+
470
+ **Usage**
471
+
472
+ ```
473
+ $ zowe mat monitor overview [options]
474
+ ```
475
+
476
+ **Options**
477
+ `--profile` _(string)_
478
+ Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
479
+
480
+ `--mon_num` _(number)_
481
+ Specifies the unique monitor number of the measurement.
482
+
483
+ **Examples**
484
+
485
+ - Get the measurement overview details for monitor number 5:
486
+
487
+ ```
488
+ $ zowe mat monitor overview --mon_num 5
489
+ ```
490
+
491
+ - Get the measurement overview details for the latest monitor in the TESTPROF profile:
492
+
493
+ ```
494
+ $ zowe mat monitor overview --profile TESTPROF
495
+ ```
496
+
497
+ - Get the measurement overview details for monitor number 5, with the specific MAT profile details defined:
498
+
499
+ ```
500
+ $ zowe mat monitor overview --mon_num 5 --host "example.com" --port 12345 --user johndoe --password qwerty
501
+ ```
502
+
503
+ The following **subgroups** are available for the MONITOR command group:
504
+
505
+ ### delayview
506
+
507
+ The commands from the DELAYVIEW group enable you to get the DelayView measurement details.
508
+
509
+ **Usage**
510
+
511
+ ```
512
+ $ zowe mat monitor delayview <command>
513
+ ```
514
+
515
+ The following **commands** are available for the DELAYVIEW group:
516
+
517
+ #### delay | de
518
+
519
+ Get the delay details for the measurement.
520
+
521
+ **Usage**
522
+
523
+ ```
524
+ $ zowe mat monitor delayview delay [options]
525
+ ```
526
+
527
+ **Options**
528
+ `--profile` _(string)_
529
+ Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
530
+
531
+ `--mon_num` _(number)_
532
+ Specifies the unique monitor number of the measurement.
533
+
534
+ **Examples**
535
+
536
+ - Get the DelayView measurement details for monitor number 5:
537
+
538
+ ```
539
+ $ zowe mat monitor delayview delay --mon_num 5
540
+ ```
541
+
542
+ - Get the DelayView measurement details for the latest monitor in the TESTPROF profile:
543
+
544
+ ```
545
+ $ zowe mat monitor delayview delay --profile TESTPROF
546
+ ```
547
+
548
+ - Get the DelayView measurement details for monitor number 5, with the specific MAT profile details defined:
549
+
550
+ ```
551
+ $ zowe mat monitor delayview delay --mon_num 5 --host "example.com" --port 12345 --user johndoe --password qwerty
552
+ ```
553
+
554
+ #### address | ad
555
+
556
+ Get the delay address details for the measurement.
557
+
558
+ **Usage**
559
+
560
+ ```
561
+ $ zowe mat monitor delayview address [options]
562
+ ```
563
+
564
+ **Options**
565
+ `--profile` _(string)_
566
+ Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
567
+
568
+ `--mon_num` _(number)_
569
+ Specifies the unique monitor number of the measurement.
570
+
571
+ `--majorcategory` _(string)_
572
+ Specifies the major delay category name identified for the analysis item (e.g. `--majorcategory "PC routine delay"`). You get the majorcategory value from the 'delayview delay' command response.
573
+
574
+ `--minorcategory` _(string)_
575
+ Specifies the minor delay category name identified for the analysis item (e.g. `--minorcategory "PC CALL"`). You get the minorcategory value from the 'delayview delay' command response.
576
+
577
+ **Examples**
578
+
579
+ - Get the delay address details for majorcategory "PC routine delay" and minorcategory "PC CALL" for monitor number 5:
580
+
581
+ ```
582
+ $ zowe mat monitor delayview address --mon_num 5 --majorcategory "PC routine delay" --minorcategory "PC CALL"
583
+ ```
584
+
585
+ - Get the delay address details for majorcategory "PC routine delay" and minorcategory "PC CALL" for the latest monitor in the TESTPROF profile:
586
+
587
+ ```
588
+ $ zowe mat monitor delayview address --profile TESTPROF --majorcategory "PC routine delay" --minorcategory "PC CALL"
589
+ ```
590
+
591
+ - Get the delay address details for majorcategory "PC routine delay" and minorcategory "PC CALL" for monitor number 5, with the specific MAT profile details defined:
592
+
593
+ ```
594
+ $ zowe mat monitor delayview address --mon_num 5 --majorcategory "PC routine delay" --minorcategory "PC CALL" --host "example.com" --port 12345 --user johndoe --password qwerty
595
+ ```
596
+
597
+ ### codeview
598
+
599
+ The commands from the CODEVIEW group enable you to get the CodeView measurement details.
600
+
601
+ **Usage**
602
+
603
+ ```
604
+ $ zowe mat monitor codeview <command>
605
+ ```
606
+
607
+ The following **commands** are available for the CODEVIEW group:
608
+
609
+ #### module | mod
610
+
611
+ Get the CodeView measurement details in Module mode.
612
+
613
+ **Usage**
614
+
615
+ ```
616
+ $ zowe mat monitor codeview module [options]
617
+ ```
618
+
619
+ **Options**
620
+ `--profile` _(string)_
621
+ Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
622
+
623
+ `--mon_num` _(number)_
624
+ Specifies the unique monitor number of the measurement.
625
+
626
+ **Examples**
627
+
628
+ - Get the CodeView measurement details in Module mode for monitor number 5:
629
+
630
+ ```
631
+ $ zowe mat monitor codeview module --mon_num 5
632
+ ```
633
+
634
+ - Get the CodeView measurement details in Module mode for the latest monitor in the TESTPROF profile:
635
+
636
+ ```
637
+ $ zowe mat monitor codeview module --profile TESTPROF
638
+ ```
639
+
640
+ - Get the CodeView measurement details in Module mode for monitor number 5, with the specific MAT profile details defined:
641
+
642
+ ```
643
+ $ zowe mat monitor codeview module --mon_num 5 --host "example.com" --port 12345 --user johndoe --password qwerty
644
+ ```
645
+
646
+ #### csect | cs
647
+
648
+ Get the CodeView measurement details in Csect mode.
649
+
650
+ **Usage**
651
+
652
+ ```
653
+ $ zowe mat monitor codeview csect [options]
654
+ ```
655
+
656
+ **Options**
657
+ `--profile` _(string)_
658
+ Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
659
+
660
+ `--mon_num` _(number)_
661
+ Specifies the unique monitor number of the measurement.
662
+
663
+ **Examples**
664
+
665
+ - Get the CodeView measurement details in Csect mode for monitor number 5:
666
+
667
+ ```
668
+ $ zowe mat monitor codeview csect --mon_num 5
669
+ ```
670
+
671
+ - Get the CodeView measurement details in Csect mode for the latest monitor in the TESTPROF profile:
672
+
673
+ ```
674
+ $ zowe mat monitor codeview csect --profile TESTPROF
675
+ ```
676
+
677
+ - Get the CodeView measurement details in Csect mode for monitor number 5, with the specific MAT profile details defined:
678
+
679
+ ```
680
+ $ zowe mat monitor codeview csect --mon_num 5 --host "example.com" --port 12345 --user johndoe --password qwerty
681
+ ```
682
+
683
+ #### histogram | hsg
684
+
685
+ Get the Histogram details for the measurement.
686
+
687
+ **Usage**
688
+
689
+ ```
690
+ $ zowe mat monitor codeview histogram [options]
691
+ ```
692
+
693
+ **Options**
694
+ `--profile` _(string)_
695
+ Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
696
+
697
+ `--mon_num` _(number)_
698
+ Specifies the unique monitor number of the measurement.
699
+
700
+ `--module` _(string)_
701
+ Specifies the module name that you request the Histogram data for. You get the module value from the 'codeview csect' or from the 'codeview module' command response. The module name can be empty (e.g., --module "IGZCPAC" or --module '""').
702
+
703
+ `--csect` _(string)_
704
+ Specifies the CSECT name that you request the Histogram data for. You get the csect value from the 'codeview csect' command response. The CSECT name can be empty (e.g., --csect "TUNCOB01" or --module '""').
705
+
706
+ `--top` _(number)_
707
+ Specifies the maximum number of the top consuming CSECT activity locations that you want to obtain in the response (e.g., --top 5). If you specify --top 0, you get the list of all CSECT activity locations that MAT has detected during the measurement. The --top parameter is optional. Values: numbers between 0 and 300.
708
+
709
+ `--group` _(number)_
710
+ Specifies the histogram group size parameter that defines the resolution of the histogram. If you do not specify the group parameter, the group size defaults to 4 bytes (e.g., --group 32). If program listing is registered with MAT, the group parameter is ignored. The --group parameter is optional.
711
+
712
+ `--listing` _(boolean)_
713
+ Enables you to retrieve program listing details that pertain to the specific CSECT and statement. To use the listing retrieval option, you must install and configure the Endevor® Web Services and have the program listing for the specific measurement registered with MAT. The source code listing is retrieved through Endevor® footprints for Cobol, C/C++, and Assembler programs. The program listing file is downloaded to your local directory that you specified with the 'listingDir' parameter for your MAT configuration profile. When you request the histogram details with the '--listing' option, the 'histogram' command returns the additional 'listing' column that contains a reference to the program listing with the specific CSECT name, program type, line and column number that pertain to the requested CSECT and statement, for example, c:\listings\SA420LE.asm:382:51. If you use Visual Studio Code (VS Code) IDE, you can click on the reference in the command response in your VS Code terminal to navigate directly to the indicated source program location. The --listing parameter is optional.
714
+
715
+ `--endevor-host` / `--endevor-port` / `--endevor-base-path` _(required for `--listing`)_
716
+ The Endevor® Web Services host/port that are used to fetch the listing must be configured locally to ensure security. Set the host and port details via the following parameters within every request or via one-time configuration of the ZOWE_OPT_ENDEVOR_HOST or ZOWE_OPT_ENDEVOR_PORT environment variables. To provide credentials, specify--endevor-user/--endevor-password (or ZOWE_OPT_ENDEVOR_USER/ZOWE_OPT_ENDEVOR_PASSWORD), or add --endevor-reuse-mat-credentials to reuse the MAT profile credentials. Run --help on this command for the full list of --endevor-* options.
717
+
718
+ **Examples**
719
+
720
+ - Get the Histogram details with the group size defaulting to 4 bytes for monitor number 5, CSECT name TUNCOB01, module name RUNCOB:
721
+
722
+ ```
723
+ $ zowe mat monitor codeview histogram --mon_num 5 --csect "TUNCOB01" --module "RUNCOB"
724
+ ```
725
+
726
+ - Get the Histogram details for the latest monitor in the TESTPROF profile for CSECT name TUNCOB01, empty module name, with the group size value set to 32 bytes, and limit the number of returned rows to 5 top consumers:
727
+
728
+ ```
729
+ $ zowe mat monitor codeview histogram --profile TESTPROF --csect "TUNCOB01" --module '""' --top 5 --group 32
730
+ ```
731
+
732
+ - Get the Histogram details for monitor number 5, CSECT name TUNCOB01, and module name RUNCOB, limit the number of returned records to 5 top consumers, and request the listing details using the MAT profile credentials:
733
+
734
+ ```
735
+ $ zowe mat monitor codeview histogram --mon_num 5 --csect "TUNCOB01" --module "RUNCOB" --top 5 --listing --endevor-host "https://host.net" --endevor-port "31111" --endevor-base-path "EndevorService/rest" --endevor-reuse-mat-credentials
736
+ ```
737
+
738
+ - Get the Histogram details for monitor number 5, CSECT name TUNCOB01, and module name RUNCOB, request the listing details with provided credentials:
739
+
740
+ ```
741
+ $ zowe mat monitor codeview histogram --mon_num 5 --csect "TUNCOB01" --module "RUNCOB" --listing --endevor-host "https://host.net" --endevor-port "31111" --endevor-base-path "EndevorService/rest" --endevor-user "USER" --endevor-password "PASS"
742
+ ```
743
+
744
+ - Get the Histogram details for monitor number 5, CSECT name TUNCOB01, and module name RUNCOB, request the listing details with the one-time export of the Endevor arguments as environment variables:
745
+
746
+ ```
747
+ $ export ZOWE_OPT_ENDEVOR_HOST="https://host.net"
748
+ $ export ZOWE_OPT_ENDEVOR_PORT="31111"
749
+ $ export ZOWE_OPT_ENDEVOR_BASE_PATH="EndevorService/rest"
750
+ $ export ZOWE_OPT_ENDEVOR_USER=USER
751
+ $ export ZOWE_OPT_ENDEVOR_PASSWORD=PASS
752
+ $ zowe mat monitor codeview histogram --mon_num 5 --csect "TUNCOB01" --module "RUNCOB" --listing
753
+ ```
754
+
755
+ - Get the Histogram details with the group size defaulting to 4 bytes for monitor number 5, CSECT name TUNCOB01, module name RUNCOB, with the specific MAT profile details defined:
756
+
757
+ ```
758
+ $ zowe mat monitor codeview histogram --mon_num 5 --csect "TUNCOB01" --module "RUNCOB" --host "example.com" --port 12345 --user johndoe --password qwerty
759
+ ```
760
+
761
+ #### callerid | cil
762
+
763
+ Get the CodeView CallerID details for the specific CSECT and module.
764
+
765
+ **Usage**
766
+
767
+ ```
768
+ $ zowe mat monitor codeview callerid [options]
769
+ ```
770
+
771
+ **Options**
772
+ `--profile` _(string)_
773
+ Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
774
+
775
+ `--mon_num` _(number)_
776
+ Specifies the unique monitor number of the measurement.
777
+
778
+ `--module` _(string)_
779
+ Specifies the module name that you request the CallerID details for. You get the module value from the 'codeview csect' or from the 'codeview module' command response. The module name can be empty (e.g., --module "IGZCPAC" or --module '""').
780
+
781
+ `--csect` _(string)_
782
+ Specifies the CSECT name that you request the CallerID details data for. You get the csect value from the 'codeview csect' command response. The CSECT name can be empty (e.g., --csect "TUNCOB01" or --csect '""').
783
+
784
+ **Examples**
785
+
786
+ - Get the CallerID details for monitor number 5, CSECT name TUNCOB01, and module name RUNCOB:
787
+
788
+ ```
789
+ $ zowe mat monitor codeview callerid --mon_num 5 --csect "TUNCOB01" --module "RUNCOB"
790
+ ```
791
+
792
+ - Get the CallerID details for the latest monitor in the profile for CSECT name TUNCOB01, and empty module name:
793
+
794
+ ```
795
+ $ zowe mat monitor codeview callerid --profile TESTPROF --csect "TUNCOB01" --module '""'
796
+ ```
797
+
798
+ - Get the CallerID details for monitor number 5, CSECT name TUNCOB01, and module name RUNCOB, with the specific MAT profile details defined:
799
+
800
+ ```
801
+ $ zowe mat monitor codeview callerid --mon_num 5 --csect "TUNCOB01" --module "RUNCOB" --host "example.com" --port 12345 --user johndoe --password qwerty
802
+ ```
803
+
804
+ ### db2
805
+
806
+ The commands from the DB2 group enable you to get the DB2 measurement details.
807
+
808
+ **Usage**
809
+
810
+ ```
811
+ $ zowe mat monitor db2 <command>
812
+ ```
813
+
814
+ The following **commands** are available for the DB2 group:
815
+
816
+ #### db2view | db2
817
+
818
+ Get the DB2View details for the measurement.
819
+
820
+ **Usage**
821
+
822
+ ```
823
+ $ zowe mat monitor db2 db2view [options]
824
+ ```
825
+
826
+ **Options**
827
+ `--profile` _(string)_
828
+ Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
829
+
830
+ `--mon_num` _(number)_
831
+ Specifies the unique monitor number of the measurement.
832
+
833
+ `--top` _(number)_
834
+ Specifies the maximum number of the top consuming DB2 statements that you want to obtain in the response (e.g., --top 5). If you specify --top 0, you get the list of of all DB2 statements that MAT has detected during the measurement. The --top parameter is optional. Values: numbers between 0 and 300.
835
+
836
+
837
+ **Examples**
838
+
839
+ - Get the DB2View details for monitor number 5:
840
+
841
+ ```
842
+ $ zowe mat monitor db2 db2view --mon_num 5
843
+ ```
844
+
845
+ - Get the DB2View details for the latest monitor in the profile, with the top consumer limitation set to 5 top consumers:
846
+
847
+ ```
848
+ $ zowe mat monitor db2 db2view --profile TESTPROF --top 5
849
+ ```
850
+
851
+ - Get the DB2View details for monitor number 5, with the specific MAT profile details defined:
852
+
853
+ ```
854
+ $ zowe mat monitor db2 db2view --mon_num 5 --host "example.com" --port 12345 --user johndoe --password qwerty
855
+ ```
856
+
857
+ #### sqlstmt | sql
858
+
859
+ Get SQL details for the DB2 statement.
860
+
861
+ **Usage**
862
+
863
+ ```
864
+ $ zowe mat monitor db2 sqlstmt [options]
865
+ ```
866
+
867
+ **Options**
868
+ `--profile` _(string)_
869
+ Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
870
+
871
+ `--mon_num` _(number)_
872
+ Specifies the unique monitor number of the measurement.
873
+
874
+ `--dbrm` _(string)_
875
+ Specifies the DBRM/Package name that the requested DB2 statement belongs to (e.g., `--dbrm CUPBTSDY`). You get the dbrm value from the 'db2 db2view' command response.
876
+
877
+ `--stmtnum` _(number)_
878
+ Specifies the statement number that you request the SQL details for (e.g., `--stmtnum 464`). You get the stmtnum value from the 'db2 db2view' command response.
879
+
880
+ `--totalsamps` _(number)_
881
+ Specifies the total number of samples taken for the requested statement (e.g., `--totalsamps 1`). You get the totalsamps value from the 'db2 db2view' command response.
882
+
883
+ **Examples**
884
+
885
+ - Get the DB2 SQL statement details for monitor number 5 for DBRM CUPBTSDY, statement number 464, with total number of taken samples 1:
886
+
887
+ ```
888
+ $ zowe mat monitor db2 sqlstmt --mon_num 5 --dbrm CUPBTSDY --stmtnum 464 --totalsamps 1
889
+ ```
890
+
891
+ - Get the DB2 SQL statement details for the latest monitor in the profile, for DBRM CUPBTSDY, statement number 464, with total number of taken samples 1:
892
+
893
+ ```
894
+ $ zowe mat monitor db2 sqlstmt --profile TESTPROF --dbrm CUPBTSDY --stmtnum 464 --totalsamps 1
895
+ ```
896
+
897
+ - Get the DB2 SQL statement details for monitor number 5 for DBRM CUPBTSDY, statement number 464, with total number of taken samples 1, with the specific MAT profile details defined:
898
+
899
+ ```
900
+ $ zowe mat monitor db2 sqlstmt --mon_num 5 --dbrm CUPBTSDY --stmtnum 464 --totalsamps 1 --host "example.com" --port 12345 --user johndoe --password qwerty
901
+ ```
902
+
903
+ ### idms
904
+
905
+ The commands from the idms group enable you to get the IDMS measurement details in DML mode.
906
+
907
+ **Usage**
908
+
909
+ ```
910
+ $ zowe mat monitor idms <command>
911
+ ```
912
+
913
+ The following **commands** are available for the IDMS group:
914
+
915
+ #### dml | dml
916
+
917
+ Get the IDMS measurement details in DML mode.
918
+
919
+ **Usage**
920
+
921
+ ```
922
+ $ zowe mat monitor idms dml [options]
923
+ ```
924
+
925
+ **Options**
926
+ `--profile` _(string)_
927
+ Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
928
+
929
+ `--mon_num` _(number)_
930
+ Specifies the unique monitor number of the measurement.
931
+
932
+ **Examples**
933
+
934
+ - Get the dml measurement details for the latest monitor in the TESTPROF profile:
935
+
936
+ ```
937
+ $ zowe mat monitor idms dml --profile TESTPROF
938
+ ```
939
+
940
+ - Get the dml details of the measurement for monitor number 5:
941
+
942
+ ```
943
+ $ zowe mat monitor idms dml --mon_num 5
944
+ ```
945
+
946
+ #### module | mod
947
+
948
+ Get the IDMS measurement details.
949
+
950
+ **Usage**
951
+
952
+ ```
953
+ $ zowe mat monitor idms module [options]
954
+ ```
955
+
956
+ **Options**
957
+ `--profile` _(string)_
958
+ Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
959
+
960
+ `--mon_num` _(number)_
961
+ Specifies the unique monitor number of the measurement.
962
+
963
+ `--module` _(string)_
964
+ Specifies the module name that you request the details for. The module name can be empty (e.g., --module "IGZCPAC" or --module '""').
965
+
966
+ `--taskid` _(number)_
967
+ Specifies the identifier of the Task that you request the details for.
968
+
969
+ `--ruid` _(number)_
970
+ Specifies the identifier of the Run Unit that you request the details for.
971
+
972
+ `--linecmd` _(string)_
973
+ Specifies the line command to be used for the row data.
974
+
975
+ **Examples**
976
+
977
+ - Get the idms details of the measurement for the latest monitor in the profile:
978
+
979
+ ```
980
+ $ zowe mat monitor idms module --profile TESTPROF
981
+ ```
982
+
983
+ - Get the module details of the measurement for monitor number 5:
984
+
985
+ ```
986
+ $ zowe mat monitor idms module --mon_num 5
987
+ ```
988
+
989
+ - Specify the module taskid, ruid, and linecmd option of the measurement for the module mode for the TESTPROF profile:
990
+
991
+ ```
992
+ $ zowe mat monitor idms module --profile TESTPROF --module SQLA01D --taskid 1 --ruid 33333 --linecmd dispatch
993
+ ```
994
+
995
+ #### task | ts
996
+
997
+ Get the IDMS measurement details in Task mode.
998
+
999
+ **Usage**
1000
+
1001
+ ```
1002
+ $ zowe mat monitor idms task [options]
1003
+ ```
1004
+
1005
+ **Options**
1006
+ `--profile` _(string)_
1007
+ Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
1008
+
1009
+ `--mon_num` _(number)_
1010
+ Specifies the unique monitor number of the measurement.
1011
+
1012
+ **Examples**
1013
+
1014
+ Get the idms measurement details in Task mode for monitor number 5:
1015
+
1016
+ ```
1017
+ $ zowe mat monitor idms task --mon_num 5
1018
+ ```
1019
+
1020
+ Get the idms measurement details in Task mode for the latest monitor in the profile:
1021
+
1022
+ ```
1023
+ $ zowe mat monitor idms task --profile TESTPROF
1024
+ ```
1025
+
1026
+ ### ims
1027
+
1028
+ The commands from the ims group enable you to get the IMS measurement details.
1029
+
1030
+ **Usage**
1031
+
1032
+ ```
1033
+ $ zowe mat monitor ims <command>
1034
+ ```
1035
+
1036
+ The following **commands** are available for the IMS group:
1037
+
1038
+ #### imsview | imsv
1039
+
1040
+ Get the IMS View details for the measurement.
1041
+
1042
+ **Usage**
1043
+
1044
+ ```
1045
+ $ zowe mat monitor ims imsview [options]
1046
+ ```
1047
+
1048
+ **Options**
1049
+ `--profile` _(string)_
1050
+ Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
1051
+
1052
+ `--mon_num` _(number)_
1053
+ Specifies the unique monitor number of the measurement.
1054
+
1055
+ **Examples**
1056
+
1057
+ - Get the IMS View details for monitor number 5:
1058
+
1059
+ ```
1060
+ $ zowe mat monitor ims imsview --mon_num 5
1061
+ ```
1062
+
1063
+ - Get the IMS View details for the latest monitor in the profile:
1064
+
1065
+ ```
1066
+ $ zowe mat monitor ims imsview --profile TESTPROF
1067
+ ```
1068
+
1069
+ #### dbdname | dbd
1070
+
1071
+ Get the IMS View DBDName data.
1072
+
1073
+ **Usage**
1074
+
1075
+ ```
1076
+ $ zowe mat monitor ims dbdname [options]
1077
+ ```
1078
+
1079
+ **Options**
1080
+ `--profile` _(string)_
1081
+ Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
1082
+
1083
+ `--mon_num` _(number)_
1084
+ Specifies the unique monitor number of the measurement.
1085
+
1086
+ **Examples**
1087
+
1088
+ - Get the IMS View DBDName details for monitor number 5:
1089
+
1090
+ ```
1091
+ $ zowe mat monitor ims dbdname --mon_num 5
1092
+ ```
1093
+
1094
+ - Get the IMS View DBDName details for the latest monitor in the profile:
1095
+
1096
+ ```
1097
+ $ zowe mat monitor ims dbdname --profile TESTPROF
1098
+ ```
1099
+
1100
+ #### psbname | psb
1101
+
1102
+ Get the IMS View PSBName measurement details.
1103
+
1104
+ **Usage**
1105
+
1106
+ ```
1107
+ $ zowe mat monitor ims psbname [options]
1108
+ ```
1109
+
1110
+ **Options**
1111
+ `--profile` _(string)_
1112
+ Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
1113
+
1114
+ `--mon_num` _(number)_
1115
+ Specifies the unique monitor number of the measurement.
1116
+
1117
+ **Examples**
1118
+
1119
+ - Get the IMS View PSBName details for monitor number 5:
1120
+
1121
+ ```
1122
+ $ zowe mat monitor ims psbname --mon_num 5
1123
+ ```
1124
+
1125
+ - Get the IMS View PSBName details for the latest monitor in the profile:
1126
+
1127
+ ```
1128
+ $ zowe mat monitor ims psbname --profile TESTPROF
1129
+ ```
1130
+
1131
+ #### region | reg
1132
+
1133
+ Get the IMS View Region measurement details.
1134
+
1135
+ **Usage**
1136
+
1137
+ ```
1138
+ $ zowe mat monitor ims region [options]
1139
+ ```
1140
+
1141
+ **Options**
1142
+ `--profile` _(string)_
1143
+ Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
1144
+
1145
+ `--mon_num` _(number)_
1146
+ Specifies the unique monitor number of the measurement.
1147
+
1148
+ **Examples**
1149
+
1150
+ - Get the IMS View Region details for monitor number 5:
1151
+
1152
+ ```
1153
+ $ zowe mat monitor ims region --mon_num 5
1154
+ ```
1155
+
1156
+ - Get the IMS View Region details for the latest monitor in the profile:
1157
+
1158
+ ```
1159
+ $ zowe mat monitor ims region --profile TESTPROF
1160
+ ```
1161
+
1162
+ #### ssa | ssa
1163
+
1164
+ Get the IMS View Region measurement details.
1165
+
1166
+ **Usage**
1167
+
1168
+ ```
1169
+ $ zowe mat monitor ims ssa [options]
1170
+ ```
1171
+
1172
+ **Options**
1173
+ `--profile` _(string)_
1174
+ Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
1175
+
1176
+ `--mon_num` _(number)_
1177
+ Specifies the unique monitor number of the measurement.
1178
+
1179
+ `--call` _(string)_
1180
+ Specifies the call details for the specified monitor number or profile name.
1181
+
1182
+ `--dbdname` _(string)_
1183
+ Specifies the database details for the specified monitor number or profile name.
1184
+
1185
+ `--psbname` _(string)_
1186
+ Specifies the PSB name details for the specified monitor number or profile name.
1187
+
1188
+ **Examples**
1189
+
1190
+ - Get the IMS View SSA details for monitor number 5 with the specific MAT profile details defined:
1191
+
1192
+ ```
1193
+ $ zowe mat monitor ims ssa --mon_num 5 --call TESTCALL --dbdname TESTDBDNAME --psbname TESTPSBNAME
1194
+ ```
1195
+
1196
+ - Get the IMS View SSA details for the latest monitor in the TESTPROF profile with the specific MAT profile details defined:
1197
+
1198
+ ```
1199
+ $ zowe mat monitor ims ssa --profile TESTPROF --call TESTCALL --dbdname TESTDBDNAME --psbname TESTPSBNAME
1200
+ ```
1201
+
1202
+ #### statement | stat
1203
+
1204
+ Get the IMS View Statement measurement details.
1205
+
1206
+ **Usage**
1207
+
1208
+ ```
1209
+ $ zowe mat monitor ims statement [options]
1210
+ ```
1211
+
1212
+ **Options**
1213
+ `--profile` _(string)_
1214
+ Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
1215
+
1216
+ `--mon_num` _(number)_
1217
+ Specifies the unique monitor number of the measurement.
1218
+
1219
+ `--trancode` _(string)_
1220
+ Specifies the transaction name for specified monitor number or profile name.
1221
+
1222
+ **Examples**
1223
+
1224
+ - Get the IMS View Statement details for monitor number 5 with trancode:
1225
+
1226
+ ```
1227
+ $ zowe mat monitor ims statement --mon_num 5 --trancode TESTTRANCODE
1228
+ ```
1229
+
1230
+ - Get the IMS View Statement details for the latest monitor in the profile with trancode:
1231
+
1232
+ ```
1233
+ $ zowe mat monitor ims statement --profile TESTPROF --trancode TESTTRANCODE
1234
+ ```
1235
+
1236
+ ### tranview
1237
+
1238
+ The commands from the tranview group enable you to get the TranView measurement details.
1239
+
1240
+ **Usage**
1241
+
1242
+ ```
1243
+ $ zowe mat monitor tranview <command>
1244
+ ```
1245
+
1246
+ The following **commands** are available for the TranView group:
1247
+
1248
+ #### all | all
1249
+
1250
+ Get the TranView measurement details in Module mode.
1251
+
1252
+ **Usage**
1253
+
1254
+ ```
1255
+ $ zowe mat monitor tranview all [options]
1256
+ ```
1257
+
1258
+ **Options**
1259
+ `--profile` _(string)_
1260
+ Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
1261
+
1262
+ `--mon_num` _(number)_
1263
+ Specifies the unique monitor number of the measurement.
1264
+
1265
+ `--tran` _(string)_
1266
+ Specifies the transaction activity. Tran = N/A is displayed for the activity that could not be attributed to a particular transaction in the address space.
1267
+
1268
+ **Examples**
1269
+
1270
+ - Get the TranView measurement details for monitor number 5:
1271
+
1272
+ ```
1273
+ $ zowe mat monitor tranview all --mon_num 5
1274
+ ```
1275
+
1276
+ - Get the TranView measurement details for the latest monitor in the TESTPROF profile:
1277
+
1278
+ ```
1279
+ $ zowe mat monitor tranview all --profile TESTPROF
1280
+ ```
1281
+
1282
+ #### module | mod
1283
+
1284
+ Get the TranView measurement details.
1285
+
1286
+ **Usage**
1287
+
1288
+ ```
1289
+ $ zowe mat monitor tranview module [options]
1290
+ ```
1291
+
1292
+ **Options**
1293
+ `--profile` _(string)_
1294
+ Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
1295
+
1296
+ `--mon_num` _(number)_
1297
+ Specifies the unique monitor number of the measurement.
1298
+
1299
+ `--tran` _(string)_
1300
+ Specifies the transaction activity. Tran = N/A is displayed for the activity that could not be attributed to a particular transaction in the address space.
1301
+
1302
+ **Examples**
1303
+
1304
+ - Get the idms details of the measurement for the latest monitor in the profile:
1305
+
1306
+ ```
1307
+ $ zowe mat monitor tranview module --profile TESTPROF
1308
+ ```
1309
+
1310
+ - Get the module details of the measurement for monitor number 5:
1311
+
1312
+ ```
1313
+ $ zowe mat monitor tranview module --mon_num 5
1314
+ ```
1315
+
1316
+ - Specify the module taskid, ruid, and linecmd option of the measurement for the module mode for the TESTPROF profile:
1317
+
1318
+ ```
1319
+ $ zowe mat monitor tranview module --tran MVGT
1320
+ ```
1321
+
1322
+ #### callerid | cid
1323
+
1324
+ Get the caller identifier details.
1325
+
1326
+ **Usage**
1327
+
1328
+ ```
1329
+ $ zowe mat monitor tranview callerid [options]
1330
+ ```
1331
+
1332
+ **Options**
1333
+ `--profile` _(string)_
1334
+ Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
1335
+
1336
+ `--mon_num` _(number)_
1337
+ Specifies the unique monitor number of the measurement.
1338
+
1339
+ `--tran` _(string)_
1340
+ Specifies the transaction activity. Tran = N/A is displayed for the activity that could not be attributed to a particular transaction in the address space.
1341
+
1342
+ **Examples**
1343
+
1344
+ - Get the caller details for monitor number 5:
1345
+
1346
+ ```
1347
+ $ zowe mat monitor tranview callerid --mon_num 5
1348
+ ```
1349
+
1350
+ - Get the caller details for the latest monitor in the TESTPROF profile:
1351
+
1352
+ ```
1353
+ $ zowe mat monitor tranview callerid --profile TESTPROF
1354
+ ```
1355
+
1356
+ #### callstack | csk
1357
+
1358
+ Get CallStack data in Module mode.
1359
+
1360
+ **Usage**
1361
+
1362
+ ```
1363
+ $ zowe mat monitor tranview callstack [options]
1364
+ ```
1365
+
1366
+ **Options**
1367
+ `--profile` _(string)_
1368
+ Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
1369
+
1370
+ `--mon_num` _(number)_
1371
+ Specifies the unique monitor number of the measurement.
1372
+
1373
+ `--tran` _(string)_
1374
+ Specifies the transaction activity. Tran = N/A is displayed for the activity that could not be attributed to a particular transaction in the address space.
1375
+
1376
+ **Examples**
1377
+
1378
+ - Get the callstack details for monitor number 5:
1379
+
1380
+ ```
1381
+ $ zowe mat monitor tranview callstack --mon_num 5
1382
+ ```
1383
+
1384
+ - Get the callstack details for the latest monitor in the TESTPROF profile:
1385
+
1386
+ ```
1387
+ $ zowe mat monitor tranview callstack --profile TESTPROF
1388
+ ```
1389
+
1390
+ #### csect | csd
1391
+
1392
+ Get the CodeView details for transaction in Csect mode.
1393
+
1394
+ **Usage**
1395
+
1396
+ ```
1397
+ $ zowe mat monitor tranview csect [options]
1398
+ ```
1399
+
1400
+ **Options**
1401
+ `--profile` _(string)_
1402
+ Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
1403
+
1404
+ `--mon_num` _(number)_
1405
+ Specifies the unique monitor number of the measurement.
1406
+
1407
+ `--tran` _(string)_
1408
+ Specifies the transaction activity. Tran = N/A is displayed for the activity that could not be attributed to a particular transaction in the address space.
1409
+
1410
+ **Examples**
1411
+
1412
+ - Get the CodeView details for transaction in Csect mode for monitor number 5:
1413
+
1414
+ ```
1415
+ $ zowe mat monitor tranview csect --mon_num 5
1416
+ ```
1417
+
1418
+ - Get the CodeView details for transaction in Csect mode for the latest monitor in the TESTPROF profile:
1419
+
1420
+ ```
1421
+ $ zowe mat monitor tranview csect --profile TESTPROF
1422
+ ```
1423
+
1424
+ - Get the CodeView details for transaction in Csect mode for the monitor number 5 with specific host:
1425
+
1426
+ ```
1427
+ $ zowe mat monitor tranview csect --mon_num 5 --host \"example.com\" --port 12345 --user User1 --password qwerty
1428
+ ```
1429
+
1430
+ #### delay | dl
1431
+
1432
+ Get the delay details for the measurement.
1433
+
1434
+ **Usage**
1435
+
1436
+ ```
1437
+ $ zowe mat monitor tranview delay [options]
1438
+ ```
1439
+
1440
+ **Options**
1441
+ `--profile` _(string)_
1442
+ Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
1443
+
1444
+ `--mon_num` _(number)_
1445
+ Specifies the unique monitor number of the measurement.
1446
+
1447
+ `--tran` _(string)_
1448
+ Specifies the transaction activity. Tran = N/A is displayed for the activity that could not be attributed to a particular transaction in the address space.
1449
+
1450
+ **Examples**
1451
+
1452
+ - Get the DelayView measurement details of a transaction for monitor number 5:
1453
+
1454
+ ```
1455
+ $ zowe mat monitor tranview delay --mon_num 5
1456
+ ```
1457
+
1458
+ - Get the DelayView measurement details for the latest monitor in the TESTPROF profile:
1459
+
1460
+ ```
1461
+ $ zowe mat monitor tranview delay --profile TESTPROF
1462
+ ```
1463
+
1464
+ - Get the DelayView measurement details for monitor number 5, with the specific MAT profile details defined:
1465
+
1466
+ ```
1467
+ $ zowe mat monitor tranview delay --mon_num 5 --host \"example.com\" --port 12345 --user User1 --password qwerty
1468
+ ```
1469
+
1470
+ #### stat | cis
1471
+
1472
+ Get the CICS statistics details.
1473
+
1474
+ **Usage**
1475
+
1476
+ ```
1477
+ $ zowe mat monitor tranview stat [options]
1478
+ ```
1479
+
1480
+ **Options**
1481
+ `--profile` _(string)_
1482
+ Specifies the name of the profile that you want to analyze. When you specify the profile name, you get the data for the latest measurement within the specified profile.
1483
+
1484
+ `--mon_num` _(number)_
1485
+ Specifies the unique monitor number of the measurement.
1486
+
1487
+ `--tran` _(string)_
1488
+ Specifies the transaction activity. Tran = N/A is displayed for the activity that could not be attributed to a particular transaction in the address space.
1489
+
1490
+ `--type` _(string)_
1491
+ Specifies the type of CICS Transaction.
1492
+ Default value: DISP
1493
+
1494
+ **Examples**
1495
+
1496
+ - Get the CICS statistic details for monitor number 5:
1497
+
1498
+ ```
1499
+ $ zowe mat monitor tranview stat --mon_num 5 --type DB
1500
+ ```
1501
+
1502
+ - Get the CICS statistics details for the latest monitor in the TESTPROF profile:
1503
+
1504
+ ```
1505
+ $ zowe mat monitor tranview stat --profile TESTPROF
1506
+ ```
1507
+
1508
+ # Uninstall the MAT Analyze Plug-in for Zowe CLI
1509
+
1510
+ To uninstall the MAT Analyze plug-in for Zowe CLI, issue the following command:
1511
+
1512
+ ```
1513
+ $ zowe plugins uninstall @broadcom/mat-analyze-for-zowe-cli
1514
+ ```