SAS® support for releases of IBM z/OS operating system


All releases at Standard Support and Limited Support will run successfully on all current IBM mainframe hardware and operating system releases. When new z/OS systems or operating system software goes GA (General Availability) SAS will support them, although it might not support all new features. Any necessary fixes for specific hardware or software are noted below. Most older releases of SAS also run successfully on current IBM machines and operating system releases, but they are not tested, and the support level guidelines apply. SAS recommends upgrading to the latest release and applying the most current maintenance and hot fixes for that release.

SAS support levels are documented on the SAS Technical Support Policies web page.

See the Supported Operating Systems web page for a summarized IBM and SAS Support Matrix.

System requirements for recent releases are available at the Install Center web page.

Technical Support hot fix and service pack information (for SAS® 9.1.3 only) is located at the Technical Support Hot Fixes web page.

Issues by z/OS Release

IMPORTANT: If you are upgrading through multiple z/OS releases, it is essential that you review the issues for each intervening release.
For example, if you are upgrading from z/OS 1.11 to z/OS 2.1, look at notes for z/OS 1.12, 1.13, and 2.1.

 

Release of z/OSAssociated SAS Notes
z/OS 3.1n/a
z/OS 2.5
  • See SAS KB0036384, "Accessing DB2 when SAS® is running under z/OS 2.5 might result in the code not executing"
z/OS 2.4
  • See SAS Note 65015, "Running SASCP under z/OS 2.4 can result in S13E during SAS® termination"
z/OS 2.3
z/OS 2.2
  • See SAS Note 56699, "zNFSC consumes more CPU time in z/OS 2.2 and might cause a system abend code EC6"
  • See SAS Note 56774, "Creating or updating a file might cause corruption or failure in a zFS file system under z/OS Version 2 Release 2 (V2R2)"
  • See SAS Note 56860, "The IBM Red Alert "z/OS Unicode Services Conversion Information Service fails after December 15, 2015" affects all releases of SAS® software"
  • See SAS Note 58738, "IBM HTTP server powered by Apache is supported in SAS® 9.4 TS1M3 under z/OS"
z/OS 2.1
  • See SAS Note 42735, "Support for the RACF profile BPX.DEFAULT.USER is dropped in z/OS 2.1"
  • If you have SAS/ACCESS® Interface to DB2, see SAS Note 51267, "Running z/OS V2R1 while accessing DB2 might result in errors"
  • See SAS Note 51319, "SAS® servers spawned by the SAS/CONNECT® Spawner and SAS® Object Spawner abend with a system 0C4-10 after the system has been upgraded to z/OS 2.1"
  • See SAS Note 56860, "The IBM Red Alert "z/OS Unicode Services Conversion Information Service fails after December 15, 2015" affects all releases of SAS® software"
z/OS 1.13
  • See SAS Note 45793, "Processing concatenated files that include a missing member causes your SAS® session to fail (or abend) with a 0C4 error."
  • See SAS Note 56860, "The IBM Red Alert "z/OS Unicode Services Conversion Information Service fails after December 15, 2015" affects all releases of SAS® software"
z/OS 1.12
  • See SAS Note 41261, "A SAS® job that is running in a z/OS 1.12 operating environment might stop responding when an external file I/O error occurs."
  • See SAS Note 42473, "A SAS® 9.2 installation in a z/OS operating environment becomes unresponsive and the metadata stops deploying."
  • If you have modified SAS Connect Spawner or Object Spawner scripts to enable the use of authorized commands, see SAS Note 44499, "SAS®9 spawners and the tsocmd UNIX System Services (USS) utility in the IBM z/OS 1.12 operating system."
  • Important: z/OS 1.12 sites that also use Computer Associates' TSO/MON® must also see SAS Note 44042, "Calculations in SAS® programs might be inaccurate and might cause errors after you upgrade to the z/OS 1.12 operating system."
  • Important: Beginning with z/OS 1.9, it became optional to move the PCCA control block above the 16M line in memory, and this became the default setting in z/OS 1.12. If your site is running with the PCCA above the line, SAS 8.2 and SAS 6.09E will abend at initialization with an 0C4. If you are still running these releases, you should verify that you have applied the fixes in the following SAS notes:
    • Version 6.09E: V6-SYS.SYS-H038
    • Version 8.2: See SAS Note 19438, "SAS® initialization ends abnormally with an 0C4 error when PCCA moves above the 16M line under Release 1.9 and later of z/OS."
  • See SAS Note 56860, "The IBM Red Alert "z/OS Unicode Services Conversion Information Service fails after December 15, 2015" affects all releases of SAS® software"
z/OS 1.11
  • See SAS Note 38132, "SAS® 9.1.3 requires Java 1.4.2 Service Refresh 13, Fix Pack 2 or higher in z/OS 1.11 operating environments."
  • See SAS Note 56860, "The IBM Red Alert "z/OS Unicode Services Conversion Information Service fails after December 15, 2015" affects all releases of SAS® software"
z/OS 1.10
  • See SAS Note 35332, "The message 'Libname libref is not assigned' might appear if you do not specify an engine."
  • See SAS Note 56860, "The IBM Red Alert "z/OS Unicode Services Conversion Information Service fails after December 15, 2015" affects all releases of SAS® software"

 

Issues with Hardware or Features

 

FeatureAssociated SAS Notes
z16 hardwareNo issues to report.
z15 hardwareSAS Note 63263, "AES encryption fails when connecting to SAS® servers in z/OS environments"
z14 hardware

SAS Note 63263, "AES encryption fails when connecting to SAS® servers in z/OS environments"

z10 hardwareApply the appropriate IBM PTFs for the IBM APARs documented in SAS Note 31484, "Calculations in SAS® code might be incorrect when running with HiperDispatch enabled for z10" and SAS Note 33749, "An error might occur for space that is allocated for a Virtual I/O (VIO) data set in the z/OS version V1R10 environment."
Extended Address Volume
(EAV) support		See SAS Note 35858, "SAS® support for EAV on the z/OS operating system for information."
DSNTYPE=LARGE
data sets
  • See SAS Note 17038, "Limited support in SAS® 9.1.3 SP4 for DSNTYPE=LARGE data sets when running under z/OS Releases V1R7 and later"
  • See SAS Note 34071, "An error might occur if you insert "DSNTYPE=LARGE" into a DD JCL statement for a SAS library" for information
LARGE BLOCK INTERFACE (LBI) files
  • See SAS Note 10759, "System 013-0E1 error when SAS® attempts to read a large blocksize file"
  • See SAS Note 43560, "The message 'ERROR: Undetermined I/O failure' occurs when an external file is read in SAS® 9.2"
  • See SAS Note 47240, "Large Block Interface (LBI) is not supported for SAS® libraries on tape"
  • See SAS Note 52839, "The FILEBLKSIZE option for 3490E or 3590 cannot be set to a value greater than 64K"