Thanks for confirmation Aamer, we are really looking forward for that functionality in 2023R1 OnPrem! currently, using Agent 19 for z/os on FNMW 2022R2 (onPrem) the ndi files will be produced just fine and find their way into FNMSInventory. In FNMSCompliance though they are not visable most of the time, even each having unique AgentID. I expect that this functionality (3 Layers, Guest, LPAR, Mainframe) will be solved/created in the next on Prem release like already stated. Looks like in the current release the different guests will be merged (overwritten) and sometimes even enter as "VM Host"...so still some open topics to be resoved until next release... I fully understand that this functionality is not offically supported right now (enven though Flexera provided tha Agent Install Source!) Thanks and greetings Steffen ... View more

Based on the subject of this thread, I'm assuming that you are specifically wonder what the following line of the logging indicates: 2022-06-22 14:17:15,430 [overy.NetServerGetInfo|PropertyDisco] [INFO ] Completed NetAPI discovery for device 'ordxxxxx' unsuccessfully: The network path could not be found At a low level, the "network path could not be found" message is a status returned from a call to the NetServerGetInfo Win32 network management API to attempt to retrieve information that Windows is able to identify about the computer named "ordxxxxx". The error suggests that the Windows operating system that the beacon is running on doesn't know anything about this name for a computer. For example, that may be because the computer name is not part of the same domain or network environment as where the beacon is running, and so Windows isn't aware of it. ... View more

Hi, maybe the following trigger will help you to reach your goal? The trigger automatically assigns all sites to the main beacon. Of course it can be customized if there are multiple beacons. Best Alex IF EXISTS (SELECT * FROM sys.triggers WHERE object_id = OBJECT_ID(N'[dbo].[trd_AddBeaconSiteSubnet]')) DROP TRIGGER [dbo].[trd_AddBeaconSites] GO CREATE TRIGGER [dbo].[trd_AddBeaconSiteSubnet] ON [dbo].[SiteSubnet_MT] AFTER INSERT, UPDATE AS BEGIN -- ASSIGN ALL SITE SUBNET TO MAIN BEACON AFTER INSERT AND UPDATE ON TABLE SITESUBNET_MT SET NOCOUNT ON; -- CREATE TEMP TABLE FOR IPADDRESS TO BEACON ASSIGNMENT IF OBJECT_ID('tempdb..#BeaconSiteSubnetMapping') IS NOT NULL DROP TABLE #BeaconSiteSubnetMapping CREATE TABLE #BeaconSiteSubnetMapping ( BeaconID [int] NOT NULL, SubnetID [int] NOT NULL ) -- INSERT DETAILS OF SITE SUBNET TO BEACON ASSIGNMENT INSERT INTO #BeaconSiteSubnetMapping SELECT (SELECT TOP 1 BeaconID FROM Beacon_MT) AS [BeaconID] ,SubnetID AS [SubnetID] FROM [dbo].[SiteSubnet_MT] -- CREATE SITE SUBNET TO BEACON ASSIGNMENT EXEC BeaconSiteSubnetMappingPutBatchByBeaconIDSubnetID END ... View more

Could you please check the connection details are correct for the mentioned datasource: FNMP-DW-DS on Cognos. To check this, on the Cognos UI if you are logged in as Analytics Administrator: -Click on the Manage icon 'click mark icon' around the bottom left side of the navigation bar. -Then navigate to Administration Console>Configuration>Data Source Connections. -Notice the FNMP-DW-DS group listed -Click on the above group and then click on the ‘More’ link under Actions on the right side of the page. -Then navigate to Set Properties>Connection. -Next to the ‘Connection String’ field, click on the pencil icon ‘Edit the connection string’. -Check both the ‘Native’ and ‘JDBC’ tabs to make sure connection details there are correct. Also you could perform Test connection there to see which one is failing. Thanks.     ... View more