---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# z/OS

# z/OS discovery {#ariaid-title1}

Release version: Yokohama  
Updated July 31, 2025  
![](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 identifies and collects infrastructure data from computers running the IBM z/OS operating system using the IBM zOS Server discovery pattern.
It supports discovery of z/OS servers at the infrastructure level and requires the latest Discovery and Service Mapping Patterns application for optimal functionality.
Application-level discovery on z/OS (such as DB2, IBM MQ, or WebSphere) is performed using separate application-specific patterns.
Show full answer Show less  

## Prerequisites

* The UNIX System Services (USS) must be running on port 22 on the z/OS host to enable SSH connectivity.
* Several host commands must be executable on the z/OS system, including uname, hostname, sysvar, netstat, df, ls, cat, grep, ps, and cut.
* Permissions required include write access to /tmp, read access to all user processes, and the ability to run REXX scripts.
* SSH credentials need to be configured in ServiceNow to authenticate discovery sessions.

## Data Collected and CMDB Impact

The IBM zOS Server pattern populates key configuration items (CIs) in the CMDB during horizontal discovery, including:

* **IBM zOS Server CI:** Captures hostname, OS version, operating system type (IBMZOS), manufacturer (IBM), hardware serial number, model ID (e.g., z14, z15), and management IP address.
* **IP Address CI:** Includes IPv4/IPv6 addresses, netmask (default 0.0.0.0), MAC address (or NOTFOUND if unavailable), and references to associated network adapters.
* **Network Adapter CI:** Details network interface names (or VIP if unavailable), IP addresses, netmask, MAC addresses, and references to the z/OS server CI.
* **File System CI:** Stores USS-mounted file system information such as mount point, dataset name, size, free space, and association with the z/OS server CI.

## CI Relationships

The discovery establishes important relationships between CIs, including:

* IBM zOS Server owns Network Adapters and IP Addresses.
* IBM zOS Server contains File Systems.
* IP Addresses reference Network Adapters, which in turn reference the IBM zOS Server.

## Additional Information

* For application discovery on z/OS systems, use specific application patterns for DB2, IBM MQ, and WebSphere.
* Updates and new discovery patterns are available via the ServiceNow Store, where customers can also request enhancements.
* For migration details from Probe to Pattern, refer to ServiceNow knowledge KB0694477.
* Further technical requirements and expectations are documented in the ServiceNow knowledge base article KB0623031.  
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=yokohama&pubname=yokohama-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 {#zOS-discovery__section_xtp_3v5_qhc}

{#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\] |
| IP Address \[cmdb_ci_ip_address\] | References | Network Adapter \[cmdb_ci_network_adapter\] |
| Network Adapter \[cmdb_ci_network_adapter\] | References | IBM zOS server \[cmdb_ci_ibm_zos_server\] |
| Serial Number \[cmdb_serial_number\] | References | IBM zOS server \[cmdb_ci_ibm_zos_server\] |
| File System \[cmdb_ci_file_system\] | References | IBM zOS server \[cmdb_ci_ibm_zos_server\] |
[ ]

{#zOS-discovery__table_lvt_yz5_qhc}
**Related reference**   

* [IBM Db2 on Linux database discovery](https://www.servicenow.com/docs/akQ09WsUequnMEW_K8uGwA "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/Ue4fu0dduF3ZBMjvsNfuzA "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/DDExKbYw3~OPHaxfCeegqg "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.")

