Description: z/OS is a 64-bit operating system for International Business Machines (IBM) mainframes. z/OS supports stable mainframe systems and standards such as Customer Information Control System (CICS), Common Business-Oriented Language (COBOL), Information Management System (IMS), Database 2 (Db2), Resource Access Control Facility (RACF), Systems Network Architecture (SNA), record-oriented data access methods, Restructured Extended Executor (REXX), Command List (CLIST), System Modification Program/Extended (SMP/E), Job Control Language (JCL), Time Sharing Option/ Extensions (TSO/E), and Interactive System Productivity Facility (ISPF). However, z/OS also supports 64-bit Java, C, C++, and UNIX (Single UNIX Specification) application programming interfaces and applications through UNIX System Services.
The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g. VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e. SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITEPMOECSO
Introduced By: CDCO Supported Architecture Components
Vendor Name: International Business Machines (IBM)
1.11 09/25/2009 09/25/2009
2.1 09/30/2013 09/30/2018
2.2.x 09/30/2015 09/30/2020
1.11 Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved
2.3.x Approved w/Constraints
[5, 6, 9, 10] Approved w/Constraints
[5, 6, 10, 11] Approved w/Constraints
[5, 6, 10, 11]
[1] Projects that have been deployed to a production environment may continue to use this technology. New projects must utilize a One-VA TRM approved operating system.
[2] As of April 23, 2015, per the Deputy CIO of Architecture, Strategy and Design (ASD), all technologies in use by the VA require an assessment by the VA Section 508 office. Section 508 of the Rehabilitation Act Amendments of 1998 is a federal law that sets the guidelines for technology accessibility. A VA Section 508 assessment of this technology has not been completed at the time of publication. Therefore, as of April 23, 2015 only users of this technology who have deployed the technology to the production environment, or have project design and implementation plans approved, may continue to operate this technology. In the case of a project that has implemented, or been approved for a specific site or number of users, and that project needs to expand operations to other sites or to an increased user base, it may do so as long as the project stays on the existing version of the technology that was approved or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.
[3] Configuration baseline and deployment standards for this technology that are maintained by Infrastructure Operations in ITOPS must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information.
[6] Configuration baseline and deployment standards for this technology that are maintained by Infrastructure Operations in Information Technology Operations and Services (ITOPS) must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information.
[7] Due to potential information security risks, cloud based technologies may not be used without the approval of the Enterprise Cloud Solution Office (ECSO). This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).
[8] Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (SPF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).
[10] Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.
[11] Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (PSF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).
Note: At the time of writing, version 2.4.0 is the most current version and was released on 09/30/2019. All versions under 2.x may only be approved with a baseline in place.
Vendor Provided* International Business Machines (IBM) Lifecycle Publicly Provided This link provides information on IBM lifecycle.
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.
Open Systems Adapter Support Facility (OSA/SF) This component provides a user-friendly interface for monitoring and managing the installed Open Systems Adapters (OSAs). OSA/SF includes software that runs on a personal computer communicating with the server.
Platforms and Storage
Operating Systems OS - Mainframe
This entry is an operating system.
No runtime dependencies have been identified.
CentOS Linux
VMware Photon Operating System (OS)
Java Enterprise Edition (Java EE)
Virtualization and Consolidation of Servers (Server Virtualize First)
This is a well-documented technology.
This technology is baselined by the VA.
This operating system may provide greater computation capacity for transaction and batch processing.
This technology may collect, store or transmit Personally Identifiable Information (PII) or Protected Health information (PHI) and proper security standards must be followed in these cases.
This technology is compatible with virtual machines, therefore consistent with the enterprise Server Virtualize First Policy.
Architectural Risks
This technology includes cloud-based functionality which has potential information security risks.