Displaying invalid elements
The INVELEMT view lists invalid elements that are detected from an opened distributed or customized view.
Invalid elements are typically detected when you have applied maintenance to a view to reference a new field, and that view is used in a context for a target that has not been upgraded.
If all targets are at the same level, no invalid elements are detected, and no action is required. However, at times you may detect an invalid element.
For example, when removing an obsolete field from all distributed views, the field may still be referenced by an old, customized view in a user’s library. In such cases, you must recreate the user-customized view from the currently distributed view to remove the invalid element.
The information in this topic applies to all BMC AMI Ops products.
Before you begin
Before opening the INVELEMT view, make sure that the following conditions exist:
- The CASPERM and CASTEMP registries are available in CAS.
- The PASTEMP registry is available in PAS.
- You have received messages BBMBRJ20I and BBMBRJ06I in CAS and BBMBRJ30I message in PAS.
To display the INVELEMT view
On the COMMAND line, from any BMC AMI Ops product, enter INVELEMT and press Enter.
The following figure displays a sample INVELEMT view opened from the MVMVS product:
COMMAND ===> SCR
CURR WIN ===> 1 ALT WIN ===>
W1 =INVELEMT==========SJSCJL71=*========10/20/23===14:43:08====MVMVS====D====2==================================
Invalid User Product View DistView View Source WinI JobName SysName Date Time
Element Name
XUCCPUB BMVJSL3 MVMVS SYSOVEZU BBMZAN02 Customized W1 BBM71PJU SJSC 2023/10/09 14:04:20
XUCCPUB BMVJSL3 MVMVS SYSOVERU BBMZAN02 Customized W1 BBM71PJU SJSC 2023/10/09 13:36:07
The Date and Time fields on INVELEMT view display the date and time at which the invalid element was detected for the first time in the same view and user since the CAS or PAS was started from the same system.
Suppressed BBMXBD19I message
Before BMC.AMIOPS.SPE2401, if invalid elements were detected, message BBMXBD19I was displayed in your session. Message BBMXBD19I indicated that the invalid elements were detected as displayed in the following example:
COMMAND ===>
CURR WIN ===> 1 ALT WIN ===>
>M1 =CASINFOU==========SJSC=====*========09/20/23===17:37:59====PLEXMGR==U====1=========
CAS MVS CAS MVLO MVI Maint Service A COMM M Exte XCF TCP
Name---- Name---- SSID SSID Release Level-- Level--- M Order--- L Secu Group--- Encryp
BBMHY017I Scrollable messages. For details, issue the 'HELP MSGDISPLAY' command
BBMXBD19I There were invalid elements found in form FORM00
To view the details, you must clear this message and press Enter.
In BMC.AMIOPS.SPE2401, if invalid elements are detected when you request a view, you can view the invalid elements directly. Message BBMXBD19I is not displayed.
The value in the field with the invalid element is displayed as ######## as displayed in the following example:
COMMAND ===>
CURR WIN ===> 1 ALT WIN ===>
>W1 =CASINFOU==========SJSCJL71=*========09/20/23===17:53:42====PLEXMGR==U====1=========
CAS MVS CAS MVLO MVI Maint Service A COMM M Exte XCF TCP
Name---- Name---- SSID SSID Release Level-- Level--- M Order--- L Secu Group--- Encryp
SJSCJL71 ######## JL71 MVML V7.1.00 BASE710 RSL2110 A TXV A RACF XTST36 Y
You can review the details about this invalid element from the console (job log of the target PAS or CAS) or on the INVELEMT view.
First-time detection of invalid elements
When invalid elements are detected for the first time, the console displays message BBMXB422W and related exception messages.
For example, if the invalid elements Z@TARGET, XXX0SYSN, and YCB0XXXX in the customized CASINFOU view from the PLEXMGR product are detected, message BBMXB422W and related messages are written to the system console.
In addition to the invalid element name displayed in message BBMXB422W, the related message issued on the console display the user name, product, view, type (customized or distributed), and report for which the invalid element is detected. This information helps users locate and correct the customized view or wait until all other targets in the SSI Context are upgraded to support the added elements.
The Report (INVELEMT) in the related message indicates that information about the detected invalid element is also available on the INVELEMT view.
The following figure displays an example of message BBMXB422W and related messages issued in the job log of CAS:
SDSF OUTPUT DISPLAY BBM71CJU S0840167 DSID 2 LINE 143 COLUMNS 02- 128
COMMAND INPUT ===> SCROLL ===> CSR
17.19.02 S0840167 BBMXB422W The Z@TARGET element does not exist in any of the source maps
17.19.02 S0840167 -Related:User(BMVJSL3) Prod(PLEXMGR) View(CASINFOU) Type(Customized) Report(INVELEMT)
17.19.02 S0840167 BBMXB422W The XXX0SYSN element does not exist in any of the source maps
17.19.02 S0840167 -Related:User(BMVJSL3) Prod(PLEXMGR) View(CASINFOU) Type(Customized) Report(INVELEMT)
17.19.02 S0840167 BBMXB422W The YCB0XXXX element does not exist in any of the source maps
17.19.02 S0840167 -Related:User(BMVJSL3) Prod(PLEXMGR) View(CASINFOU) Type(Customized) Report(INVELEMT)
******************************** BOTTOM OF DATA *********************************************************************
The following figure displays an example of message BBMXB422W and related messages issued in the job log of PAS:
13.36.07 S0860482 -Related:User(BMVJSL3) Prod(MVMVS) View(SYSOVERU) Type(Customized) Report(INVELEMT)
14.04.20 S0860482 BBMXB422W The XUCCPUB element does not exist in any of the source maps
14.04.20 S0860482 -Related:User(BMVJSL3) Prod(MVMVS) View(SYSOVEZU) Type(Customized) Report(INVELEMT)