--- sourceDocument: Australia IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # z/OS # z/OS discovery {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of z/OS discovery The z/OS discovery feature in ServiceNow enables discovery of computers running the IBM z/OS operating system through the IBM zOS Server pattern. This infrastructure-level discovery populates the Configuration Management Database (CMDB) with detailed z/OS server data. To discover applications running on z/OS, such as DB2, IBM MQ, or WebSphere, separate application-specific patterns should be used. Show full answer Show less To ensure accurate discovery, customers may need to update to the latest Discovery and Service Mapping Patterns application from the ServiceNow Store. The feature supports comprehensive discovery of z/OS system components and their relationships, helping maintain an accurate and connected CMDB. ## Prerequisites * Ensure UNIX System Services (USS) is running and accessible on port 22 on the z/OS system. * Verify the ability to execute key host commands such as `uname`, `hostname`, `sysvar`, `netstat`, `df`, `ls`, `cat`, `grep`, `ps`, and `cut`. * Confirm necessary permissions including write access to `/tmp`, read access to all user processes, and ability to run REXX scripts. * Create and configure SSH credentials to enable secure discovery connections. ## Key Features * **Discovery of z/OS servers:** Collects hostname, OS version, manufacturer, hardware model, serial number, and management IP address. * **Network components:** Discovers IP addresses and network adapters with details such as IP, netmask, MAC address, and network interface names. * **File system discovery:** Discovers USS-mounted file systems with attributes including mount points, volume IDs, dataset names, total size, and free space. * **CI relationships and references:** Establishes ownership and containment relationships between z/OS servers, network adapters, IP addresses, and file systems to represent infrastructure accurately in the CMDB. ## Data Collected The discovery process populates specific CMDB tables including: * **IBM zOS server \[cmdbciibmzosserver\]:** Core server attributes like name, OS version, model, and IP address. * **IP Address \[cmdbciipaddress\]:** IP details with network mask and MAC address. * **Network Adapter \[cmdbcinetworkadapter\]:** Network interface details referencing the server CI. * **File System \[cmdbcifilesystem\]:** Details of USS-mounted file systems linked to the z/OS server. ## Practical Benefits for ServiceNow Customers By implementing z/OS discovery, customers can maintain an up-to-date and detailed inventory of their mainframe infrastructure within the CMDB. This supports improved asset management, impact analysis, and operational visibility. The automated discovery of hardware, network components, and file systems enables better configuration tracking and supports integration with application-level discovery for comprehensive service mapping. Customers should ensure all prerequisites are met to enable successful discovery and leverage the latest pattern updates from the ServiceNow Store for optimal results. Discovery and Service Mapping Patterns finds computers running the z/OS operating system using the IBM zOS Server pattern. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store. ## Request new or enhanced Patterns on the ServiceNow® Store {#zOS-discovery__id_d51_3mx_qhc} Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/application/06a71b1367e4130051c9027e2685ef1e/1.6.0?referer=/store/search?listingtype=allintegrations%253Bancillary_app%253Bcertified_apps%253Bcontent%253Bindustry_solution%253Boem%253Butility%253Btemplate&q=Patterns&sl=sh) to view all the available updates and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html).{#zOS-discovery__p_d21_nfg_h1c} Note: For information on Probe to Pattern migration see the knowledge article [KB0694477](https://support.servicenow.com/kb_view.do?sysparm_article=KB0694477). The IBM zOS Server pattern performs infrastructure-level discovery for z/OS servers. To discover applications on z/OS, use application patterns, such as DB2 on Linux, WMQ On Unix, or Websphere On Unix. For more information, see [IBM z/OS Discovery requirements and expectations \[KB0623031\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0623031) article in the Now Support Knowledge Base. ## Prerequisites {#zOS-discovery__section_xzz_ngl_mbb} Verify that the UNIX System Services (USS) is running on port 22 : Verify that the USS service is running on port 22 on z/OS. Verify the required commands on the host machine : Verify that you can run the following commands on the host machine: * `uname` * `hostname` * `sysvar SYSNAME` * `netstat` * `df` * `ls` * `cat` * `grep` * `ps` * `cut` {#zOS-discovery__ul_irx_phl_mbb} Verify required permissions : Verify that you have the following permissions: * Write permission to `/tmp` * Read access to all user processes * Ability to run REXX scripts {#zOS-discovery__ul_gsg_w55_qhc} Create SSH credentials : For more information, see [SSH credentials](https://www.servicenow.com/docs/access?context=r_SSHCredentialsForm&version=australia&pubname=australia-platform-security&ft:locale=en-US). ## Data collected by Discovery during horizontal discovery {#zOS-discovery__section_nyj_dwk_mbb} Discovery populates the data in the CMDB when running the IBM zOS Server pattern. The pattern discovers USS-mounted file systems. {#zOS-discovery__table_u33_nv5_qhc__entry__2} | Field | Description | |-|-| | Name \[name\] | Hostname of the z/OS system. | | OS Version \[os_version\] | z/OS operating system version. For example: V2R5 or 3.1. | | Operating System \[os\] | Operating system type. The value is set to IBM_ZOS. | | Manufacturer \[manufacturer\] | Hardware manufacturer. The value is set to IBM. | | Serial number \[serial_number\] | Hardware chassis serial number. | | Model ID \[model_id\] | Hardware model display name based on model code lookup. For example: z14, z15, or zEnterprise 196. If the model code isn't in the lookup table, this field remains empty. | | IP Address \[ip_address\] | Management IP address used for discovery connection. | [Table 1. IBM zOS server \[cmdb_ci_ibm_zos_server\]] {#zOS-discovery__table_u33_nv5_qhc} {#zOS-discovery__table_tlp_bx5_qhc__entry__2} | Field | Description | |-|-| | IP Address \[ip_address\] | IPv4 or IPv6 address. | | Netmask \[netmask\] | Network mask for the IP address. The value is set to 0.0.0.0. | | MAC Address \[mac_address\] | Hardware MAC address. If unavailable, the value is set to NOT_FOUND. | | Nic \[nic\] | References the Network Adapter \[cmdb_ci_network_adapter\] table. | [Table 2. IP Address \[cmdb_ci_ip_address\]] {#zOS-discovery__table_tlp_bx5_qhc} {#zOS-discovery__table_r5b_qy5_qhc__entry__2} | Field | Description | |-|-| | Name \[name\] | Network interface name. If unavailable, the value is set to VIP. | | IP Address \[ip_address\] | IPv4 or IPv6 address assigned to this network adapter. | | Netmask \[netmask\] | Network mask for the adapter. The value is set to 0.0.0.0. | | MAC Address \[mac_address\] | Hardware MAC address for the network adapter. If unavailable, the value is set to NOT_FOUND. | | Configuration Item \[cmdb_ci\] | References the IBM zOS server \[cmdb_ci_ibm_zos_server\] table. | [Table 3. Network Adapter \[cmdb_ci_network_adapter\]] {#zOS-discovery__table_r5b_qy5_qhc} {#zOS-discovery__table_ir3_dz5_qhc__entry__2} | Field | Description | |-|-| | Name \[name\] | Name of the USS file system set to the mount point path. For example: /, /tmp, or /u. | | Volume ID \[volume_id\] | Volume identifier, set to the mount point path. | | Mount point \[mount_point\] | Directory path where the file system is mounted in the USS hierarchy. | | File system \[file_system\] | USS dataset name of the zFS file system. For example: OMVS.ROOT.ZFS or OMVS.TMP.ZFS. | | Size bytes \[size_bytes\] | Total capacity of the file system in kilobytes (KB), as retrieved by the df -Pkv command. | | Free space bytes \[free_space_bytes\] | Available free space in the file system in KB, as retrieved by the df -Pkv command. | | Computer \[computer\] | References the IBM zOS server \[cmdb_ci_ibm_zos_server\] table. | [Table 4. File System \[cmdb_ci_file_system\]] {#zOS-discovery__table_ir3_dz5_qhc} ## CI relationships and references {#zOS-discovery__section_xtp_3v5_qhc} The IBM zOS Server pattern creates the following relationships and references to support z/OS discovery. References link to records in other tables and don't appear in the CI Relationship \[cmdb_rel_ci\] table. {#zOS-discovery__table_lvt_yz5_qhc__entry__3} | CI | Relationship | CI | |-|-|-| | IBM zOS server \[cmdb_ci_ibm_zos_server\] | Owns::Owned by | Network Adapter \[cmdb_ci_network_adapter\] | | IBM zOS server \[cmdb_ci_ibm_zos_server\] | Owns::Owned by | IP Address \[cmdb_ci_ip_address\] | | IBM zOS server \[cmdb_ci_ibm_zos_server\] | Contains::Contained by | File System \[cmdb_ci_file_system\] | [Table 5. CI relationships] {#zOS-discovery__table_lvt_yz5_qhc} {#zOS-discovery__table_nrr_mnb_hkc__entry__3} | CI | Field | Referenced CI | |-|-|-| | IP Address \[cmdb_ci_ip_address\] | Nic \[nic\] | Network Adapter \[cmdb_ci_network_adapter\] | | Network Adapter \[cmdb_ci_network_adapter\] | Configuration Item \[cmdb_ci\] | IBM zOS server \[cmdb_ci_ibm_zos_server\] | | Serial Number \[cmdb_serial_number\] | Configuration item \[cmdb_ci\] | IBM zOS server \[cmdb_ci_ibm_zos_server\] | | File System \[cmdb_ci_file_system\] | Computer \[computer\] | IBM zOS server \[cmdb_ci_ibm_zos_server\] | [Table 6. CI references] {#zOS-discovery__table_nrr_mnb_hkc} **Related reference** * [IBM Db2 on Linux database discovery](https://www.servicenow.com/docs/JhHUSHaS2TVrfRNIwaFvyA "ServiceNow Discovery uses the Db2 on Linux discovery pattern to find IBM Db2 instances on Linux servers.") * [IBM MQ discovery](https://www.servicenow.com/docs/H3r9t4EzPBx8NRx8soHG3g "The ServiceNow Discovery application uses the WMQ On Unix and WMQ On Windows patterns to find IBM MQ (formerly IBM WebSphere MQ) resources. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.") * [IBM WebSphere Application Server discovery using patterns](https://www.servicenow.com/docs/y6cIlnSUJFNC09JJkOkrIA "The Discovery and Service Mapping Patterns application uses the Websphere On Windows and Websphere On Unix patterns to find IBM WebSphere Application Servers. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.")