SAS Institute. The Power to Know


SAS 9.1.3 (9.1 TS1M3) Hot Fixes

BASE SAS
® Software
Hot Fix Bundle E9BX03 for z/OS (OS/390)
with Asian Language Support


The following fixes are included in the E9BX03 Bundle for OS/390:Introduced
in BUNDLE:
E9BA02
SN-017049Deleted observations can get added to new data set when migratingE9BX01
E9BA03
SN-017176JDBC connection to SAS/SHARE Server encounters transcoding error fornon-English localeE9BX01
E9BA09
SN-017440SQRT function now supported in MDX code for SAS OLAP ServerE9BX01
E9BA12
SN-017694Missing Output when specifying APPLEVEL parameter on IOM Serverdefinition in SAS Management Console or OBJECTSERVERPARMS SAS OptionE9BX01
E9BA14
SN-016954SAS/Integration Technologies 9.1 Object Spawner consumes excessive CPUwhen an ERROR=122 (EIO) occursE9BX01
E9BA26
SN-017800WHERE clause is not allowed with preset indexE9BX01
E9BA27
SN-017801XMLSELECT with OMI_MATCH_CASE does not honor multiple attributes in asearchE9BX01
E9BA30
SN-017581ERROR: Invalid physical name for library XXXX is displayed when usingUpdate Table Metadata or PROC METALIB with concatenated librariesE9BX01
SN-017580ERROR: This Library is already assigned or cannot be reassignedE9BX01
SN-017849PROC METALIB fails to update an SPDS library table metadata with "Error:Invalid Option User."E9BX01
E9BA32
SN-017241"ERROR: System abend 0C4 occurred in module SASYHRE8 function YHRMHMR atoffset 000420"E9BX01
E9BA37
SN-017976Error about running out of space using PROC PRINT in certain situationsE9BX01
E9BA42
SN-018019The default value for the FTEXT= graphics option with the Japanese orKorean install is incorrectly setE9BX01
E9BA43
SN-013603IRR and INTRR function may generate INVALID ARGUMENT message in SAS 9.1E9BX01
E9BA46
SN-015522"ERROR: System abend s0C4 ocurred in module unknown - vxvtc at offset00082C"E9BX01
E9BA51
SN-018393Accessing a member from MEMLIST produces "ERROR: Invalid Device Type"E9BX01
E9BA57
SN-018011SPECIFIED RESOURCE DOES NOT EXIST message with ENCODING=(W5|W6|W9)and SPDE engineE9BX01
SN-018254MDX WHERE clause might return incorrect number of rows resulting in aperformance lossE9BX01
SN-018911"ERROR: System Exiting Status=401" message occurs when multipleprocesses update a SPD Engine data setE9BX01
E9BA62
SN-017208A long format length may cause a system error in PROC REPORTE9BX01
SN-018200FLOW option on DEFINE statement may cause system errorE9BX01
SN-018737Hot fix E9BA45 replaced by E9BA62 for z/OSE9BX01
E9BA81
SN-019166Possible memory-related failures when using the CATALOG access methodE9BX01
E9BA86
SN-019227NOWARN option for PROC APPENDE9BX01
E9BA87
SN-019218ERRORS produced when ODS PDF output contains a long bylineE9BX01
E9BA91
SN-016283A Japanese character that contains the hex value for a single or doublequote may cause the Program Editor to have an incorrect colorE9BX01
E9BB11
SN-019773Abend U1314 or traceback notes and messages attempting to read amigrated view from SASŪ 8E9BX02
E9BB17
SN-019231JAVAOBJ component object fails to free semaphoresE9BX02
SN-019812Values are quoted when DBCS value has same hex code as delimiter characterE9BX02
E9BB18
SN-019486"ERROR: Invalid memptr" and SAS session hangs when trying to access aview via a libref with the META LIBNAME engineE9BX02
E9BB50
SN-020578PROC CIMPORT generates warning: "This transport file is from an earlierSAS release"E9BX03 *
SN-017841Extraneous characters appear for catalog entry descriptions when usingPROC CIMPORTE9BX03 *
SN-020673Using PROC CIMPORT in DBCS version of SAS may result in errors orgarbage characters if transport file contains data with indexesE9BX03 *
SN-020675Garbage characters may result when using PROC CIMPORT to import atransport file containing double-byte character set dataE9BX03 *
E9BB60
SN-020908The SAS/CONNECTŪ spawner does not detect a missing SAS SVC routineE9BX03 *
E9BB65
SN-019742Attempting to connect to the SASŪ Metadata Server when the METAUSER system option contains an embedded space generates an errorE9BX03 *
E9BB66
SN-021053The SASŪ Stored Process Server and SASŪ Workspace Server load balancing is not distributed across hosts with thelowest cost algorithmE9BX03 *
E9BB68
SN-017410SAS OLAP Server process may crash if slicer contains infinite loopE9BX01
SN-017408Permission condition memory is not released when OLAP session closedE9BX01
SN-017409SAS OLAP Server performance enhancements available in SAS 9.1.3 ServicePack 4E9BX01
SN-018037PROC OLAP DEFINE statement can allow duplicate calculated members to becreatedE9BX01
SN-017931NUNIQUE values may be incorrect depending on the setting for "Maximumnumber of region execution threads"E9BX01
SN-017445Listing active queries on SAS OLAP Server can cause server crashE9BX01
SN-017523Selecting an OLAP Session in the OLAP Server monitor may cause SASManagement Console to hangE9BX01
SN-018020SAS OLAP Server may error when empty data is passed to certain SASfunctionsE9BX01
SN-017871Drilldown may cause calculated member values to return from the SASOLAP Server as missing in Service Pack 4E9BX01
SN-018018Complex MDX query within a WITH expression may generate an AccessViolationE9BX01
SN-018030SAS OLAP Server may abend with an OLS_NAMESPACEDELETE tracebackE9BX01
SN-017907OLAP cubes with deep hierarchies may return incorrect result setsE9BX01
SN-018089Detailed SAS OLAP Server logging now outputs SAS OLAP Server optionsettingsE9BX01
SN-018012Threadpool options for the SAS OLAP Server are being overwrittenE9BX01
SN-018198TKASSERT error might be received when querying an OLAP cube on Z/OSE9BX01
SN-017449NON EMPTY CROSSJOIN optimization in SAS OLAP ServerE9BX01
SN-018254MDX WHERE clause might return incorrect number of rows resulting in aperformance lossE9BX01
SN-018701Session and Global calculated members might be dropped when using NonEmptyOptimizationE9BX01
SN-018580Disabling NonEmpty Crossjoin optimization does not have any effectE9BX01
SN-018794DrillDownMemberTop function might cause crashes in the SASŪ OLAP ServerE9BX01
SN-018702Global calculated members might cause crash in SAS OLAP Server withOptimization of Non Empty CrossjoinsE9BX01
SN-018795OLAP queries might return empty results if requesting missing valuesE9BX01
SN-018796MDX iif functions that return null values might incorrectly returnempty result setsE9BX01
SN-019048Calculated measures might be dropped from the OLAP result set when usingNon Empty Crossjoin OptimizationE9BX01
SN-019164Memory degradation or Access Violation could occur when querying an OLAPcube with Member Level Security appliedE9BX01
SN-018253DBCS drillthrough labels might not be rendered correctlyE9BX01
SN-019226Sorted OLAP queries might return incorrect resultsE9BX01
SN-019314Use of global MDX String functions could halt the SAS OLAP ServerE9BX01
SN-019418AGGREGATE MDX function might cause slow query performance when memberlevel security is defined to the OLAP cubeE9BX01
SN-019725AGGREGATE functions using calculated members containing NUNIQUE measures might cause SASŪ OLAP Server to crashE9BX02
SN-019820NONEMPTYCROSSJOIN function might cause data loss in an OLAP QueryE9BX02
SN-020202Incorrect totals calculated when aggregate has members in same dimensionof the NUNIQUE measure being usedE9BX02
SN-020292SASŪ OLAP Server performance might be worse after applying hotfix E9BA34 or laterE9BX02
SN-020291SASŪ OLAP Server AGGREGATE function might return incorrect results on certain calculated membersE9BX02
SN-030537SAS MDX isEmpty function will not evaluate cells containing character dataE9BX03 *
SN-020146Total calculations might be incorrect when an NUNIQUE measure is usedE9BX02
E9BB69
SN-018812SAS Information Map might fail to open in SAS Enterprise GuideE9BX02
SN-019360"ERROR: Proc InfoMaps is not available on this operating system." on64-bit HP-UX and the mainframeE9BX02
SN-020496SAS Information Map Libname Engine might generate "ERROR: Write AccessViolation in Task"E9BX03 *
SN-020991SASŪ Information Maps with more than 1000 data items might fail to open with the SAS Information Map Libname Engine (IMLE)E9BX03 *
E9BB74
SN-017767Export and Import Wizards require Metadata Server fixesE9BX01
SN-017743Login to SAS web application fails when using an email address as theuserid with LDAP authenticationE9BX01
SN-017761Jobs that are duplicated within a Project repository may lose theirconnection to Target objectsE9BX01
SN-017860BI Manager "Import" might cause metadata to be destroyed for all stored processes that contain parameters in SAS 9.1.3 Service Pack 4E9BX01
SN-017852External table objects may get inadvertently deleted from metadata whenimporting or exporting metadata multiple timesE9BX01
SN-017855Server code does not support exporting and importing from a metadata Project repositoryE9BX01
SN-017857Exception may occur while exporting a block of objects from the DataIntegration Studio custom treeE9BX01
SN-017854Incorrect behavior might occur when all items are not selected within apackage when performing a metadata importE9BX01
SN-018452Unauthorized access to metadata server contentE9BX01
SN-030465Adding new records to a metadata repository after performing a metadata restore adds multiple metadata objects with the same internal ID valueE9BX03 *
E9BB78
SN-015924DATETIMEw.d format can produce incorrect resultsE9BX01
SN-030622Error generated when MDYAMPM format is used in a FOOTNOTEE9BX03 *
E9BB80
SN-016428DBSLICEPARM creates incorrect syntax when DB2DECPT=,E9BX01
SN-018162System abend SA03 during SAS termination when DB2 LIBNAME engine withDEFER=YES specifiedE9BX03 *
SN-020687Support for Oracle TIMESTAMP data types added in SAS 9.1.3E9BX03 *
SN-030942The WHERE clause strips trailing blanks from string literals that are concatenated with DBMS columns of type VARCHARE9BX03 *
E9BB81
SN-018463Access Violation or 0C4 abend in module SASSFM01 when using proceduresthat use multi-label formatsE9BX01
SN-020189Statistic labels in PROC TABULATE not displayed in uppercase in tableoutputE9BX02
SN-020444Error in PROC TABULATE NLS versions after applying hot fix E9BB28E9BX02
SN-020359Variable labels that contain multi-byte character set strings do notsplit correctlyE9BX02
SN-030679Page dimension "and" in PROC TABULATE not displayed in uppercase in table outputE9BX03 *
E9BB92
SN-030979Performance degradation might occur in SASŪ9 if you process VSAM files on a Remote Library Services (RLS) serverE9BX03 *
E9BB94
SN-020378A segmentation violation might occur during execution of the DOWNLOADprocedureE9BX03 *
SN-031087A floating-point exception error might occur if you use the DOWNLOAD procedure to move a file that is larger than 2 GBE9BX03 *
E9BB95
SN-017072Metadata server service might show starting state but never startE9BX03 *
SN-020274Grid sign-on fails to honor the TCPPORTFIRST and the TCPPORTLAST optionsE9BX03 *
SN-019386SAS/CONNECT may issue "Segmentation Violation In Task [ Program ]"E9BX03 *
SN-020817Using the JOBNAME= option to specify a job name in the GRDSVC_ENABLE call routineE9BX03 *
E9BB96
SN-017704An update to ensure proper authentication logging on to an IntegrationTechnology ServerE9BX01
SN-020384If your z/OS user ID begins with special characters, you cannot see pre-assigned libraries from SASŪ Enterprise GuideŪ 4.1E9BX02
SN-020418"ACCESS DENIED" authentication error is not displayed as expected whenthe Metadata server using a Japanese version of WindowsE9BX02
SN-031165IOM messages are truncated in the SASŪ Metadata Server logE9BX03 *
E9BB97
SN-017915Memory leak in transcoding routine from MBCS to MBCSE9BX03 *
SN-019088KCVT function has problem handling trailing null characterE9BX01
SN-020676PROC CIMPORT may fail or generate errors when the file contains SBCSKatakana dataE9BX03 *
SN-030987Performance problems occur in DBCS SASŪ software when you use the RLINK or DLM= options in the FILENAME statementE9BX03 *
E9BB98
SN-017745WHERE clause processing against an SQL view can cause Read Access orSegmentation ViolationsE9BX01
SN-017962The first blank space in the name literal table names gets removed whenyou set the SYSLAST macro variable or _LAST_ system optionE9BX01
SN-017876Creating index may cause SAS to loopE9BX01
SN-017981Incorrect output with WHERE and BY statementsE9BX01
SN-015813Read Access Violation in Task (CONNECT) caused by long commentsE9BX01
SN-018156Invoking an autocall macro which is stored as a SOURCE entry within acatalog may cause errorsE9BX01
SN-018305Garbage characters in SAS log when localized DBCS SAS is used withproducts related to the Workspace serverE9BX01
SN-018396Queries or WHERE clauses run against large data sets can causeSAS/SHARE server to hangE9BX01
SN-015882A Japanese character that contains the hex value for a single or doublequote may be misinterpreted by the SAS tokenizerE9BX01
SN-019372Performance is poor in the SQL procedure when you use the COUNT(Distinctxxxx) functionE9BX02
SN-019601The option VALIDVARNAME=UPCASE is not working as expectedE9BX02
SN-019978Specifying LOGPARM system option may generate INSUFFICIENTAUTHORIZATION messagesE9BX02
SN-019984Output in the listing is truncated using the DBCS version of SASE9BX02
SN-019344SAS may ignore indexes during query on 64-Bit UNIX systemsE9BX02
SN-019578Update Flags from PROC SQL views are propagated by SAS procedures withOUT= optionE9BX02
SN-020208The ACCESS=READONLY option in the CATNAME statement is not workingcorrectlyE9BX02
SN-020562PROC APPEND step may damage BASE data setE9BX02
SN-021003The LOGPARM path directive %v or #v might result in an unresponsiveprocessesE9BX03 *
SN-030428Aliased constant values become missing in outer joins and unionsE9BX03 *
SN-030390Improvements are now available in relational database optimization via PROC SQLE9BX03 *
SN-019655Filter behavior inconsistent between SASŪ Web Report Studio 3.1 and SASŪ Information Map StudioE9BX03 *
SN-031300Poor performance occurs when you use views that consist of inner joins from DBMS tablesE9BX03 *
E9BB99
SN-017873Extra WHERE clause may get added to query passed to databasesE9BX01
SN-017888Segmentation Violation error issued when using PROC SQL and SAS/ACCESSwith a LENGTH= option larger than 32E9BX01
SN-018108Segmentation violation when executing multiple queries against a PROCSQL view containing a LIBNAME statementE9BX01
SN-018176Import of table through Information Map Library Engine deletes physicaltableE9BX01
SN-020479Batch jobs might end with a return code of 4 with no warning in the SASlogE9BX03 *
SN-018487Compress() function returns incorrect results when used on PROC SQLINSERT statement after applying SAS 9.1.3 Service Pack 4E9BX01
SN-016074"WARNING: At least one nonessential grouping column reference has beenremoved from a GROUP BY's reference list"E9BX01
SN-019170Errors issued when integer references for column is used in a PROC SQLGROUP BY statementE9BX01
SN-019372Performance is poor in the SQL procedure when you use the COUNT(Distinctxxxx) functionE9BX02
SN-019527Specifying the NOIPASSTHRU option in PROC SQL does not disable implicitpassthruE9BX02
SN-016547Correlated subqueries using column aliases may not be passed to yourdbms when using SAS/ACCESS LIBNAME statementE9BX02
SN-019930Using more than 36 tables in a UNION operation within an SQL proceduregenerates an error messageE9BX02
SN-020130Aliases columns or aliased tables in the SQL procedure blocks ImplicitPass-ThroughE9BX03 *
SN-030428Aliased constant values become missing in outer joins and unionsE9BX03 *
SN-020116SAS/ACCESSŪ software fails to use table aliases correctly when you use in-line SELECT statementsE9BX03 *
SN-020162Using functions without parameters in WHERE clauses can block ImplicitPass-ThroughE9BX03 *
SN-020126SAS/ACCESSŪ software now provides full support of the INNER JOIN syntaxE9BX03 *
SN-020123Incorrect SQL text is generated when inner and left joins are usedE9BX03 *
SN-020125Using implicit pass-through might cause an incorrect table referenceassignmentE9BX03 *
SN-020129An incorrect Implicit Pass-Through query is generated when you use acombination of inner and outer JoinsE9BX03 *
SN-020122Performance issues occur because SQL code is not passed to the databaseE9BX03 *
SN-030390Improvements are now available in relational database optimization via PROC SQLE9BX03 *
SN-019655Filter behavior inconsistent between SASŪ Web Report Studio 3.1 and SASŪ Information Map StudioE9BX03 *
SN-020635Incorrect textualization of SQL Implicit Pass-Through queries occurswhen you combine multiple inner joins with one or more outer joinsE9BX03 *
SN-030942The WHERE clause strips trailing blanks from string literals that are concatenated with DBMS columns of type VARCHARE9BX03 *
SN-030923Aliased summary functions in Base SASŪ software are not passed to databasesE9BX03 *
SN-030893Using an ORDER BY clause in the SQL procedure causes performance problemsE9BX03 *
SN-031102A segmentation-violation error might occur after you apply Hot Fix E9BA83 and you access OracleE9BX03 *
SN-031191Support is now available for the PROC SQL CREATE TABLE statement for the SASŪ Scalable Performance Data ServerŪ E9BX03 *
SN-031122SQLPLAN internal errors might occur when you select columns from an SQL viewE9BX03 *
SN-031121Implicit Pass-Through errors occur when accessing Oracle tables E9BX03 *
SN-031291Errors occur in SASŪ Scalable Performance Data ServerŪ for numeric columns that are defined with the MISSING statement when it is used in WHERE processingE9BX03 *
SN-031211Errors occur in the SQL procedure's Implicit Pass-Through facility after you apply hot fixes E9BB72, E9BB76, and E9BB80E9BX03 *
SN-031249SQLPLAN errors occur when you reference a calculated column on an SQL WHERE clause E9BX03 *
E9BC02
SN-019115TRANWRD() function has different performance in SAS 6, and SAS 8 and SAS9.1.3E9BX01
SN-031391Transcoding problem occurs between SASŪ Japanese encoding shift-jis and EUCE9BX03 *
E9BC05
SN-017270Style not applied properly when sending ODS emailE9BX01
SN-017354SMTP email only uses the e-mail user ID (rather than the full e-mail address) for authenticationE9BX01
SN-007782Time stamp calculation when emailing from OS/390E9BX01
SN-019638Sending e-mail attachments using SMTP causes a read-access violationE9BX02
SN-020323SASŪ 9.1.3 and earlier SMTP e-mails do not timeout when block waiting for a response from a SMTP serverE9BX02
SN-018044Using SMTP e-mail with SASŪ 9.1.3 (English version with DBCS and Unicode support) might cause truncated or missing e-mail outputE9BX03 *
SN-031148Unable to authenticate e-mail on z/OSE9BX03 *
E9BC06
SN-017147Output to RECFM=FB SASLIST file may contain carriage controlE9BX01
SN-017380Client TSO session loops while processing FSBROWSE on library allocatedto a SAS/SHARE serverE9BX01
SN-019281PROC CIMPORT fails when the transport file is a member of an uncatalogedpartitioned data setE9BX03 *
SN-017797"ERROR: Physical file does not exist,SYS06144.T115731.RA000.N389610T.INCL.H04" message from %INCLUDEE9BX01
SN-013425Autoexec may continue processing when leaving MENU entry defined toSHARE server in SAS/AFE9BX01
SN-018423Control incorrectly appears to return to SAS/AF application when sortingdata on the mainframeE9BX01
SN-013720TSO may hang when leaving SAS after running SAS/AF application withSAS/SHAREE9BX01
SN-016476System abend 0C4 in module SASTKE9BX01
SN-018430ERROR: Unable to initialize TCP/IP subsystem returns Condition Code 0E9BX01
SN-019299Division-by-zero processing causes severe performance degradationE9BX01
SN-020327Contents of a variable change when you pass the variable to theFILEEXIST functionE9BX02
SN-018637ALTLOG and ALTLIST files may be missing if directed to HFSE9BX01
SN-019065DISP is ignored in LIBNAME statement when existing allocation alreadyexistsE9BX01
SN-019522The FILENAME function for an HFS pathSAS argument generates incorrectresultsE9BX01
SN-017038Limited support in SASŪ 9.1.3 SP4 for DSNTYPE=LARGE data sets when running under z/OS Releases V1R7 and laterE9BX02
SN-019842SASŪ9 software reads all generations of a generation data group controlled by the Storage Management SubsystemE9BX02
SN-020035The RELEASE procedure can damage a currently assigned SAS data library,resulting in an I/O error or U315 abnormal ending messageE9BX02
SN-020459Performance issues found in SASŪ software memory management on the z/OS platformE9BX02
SN-020583Concatenation of 257 physical sequential data sets fails when you run SASŪ software on z/OSE9BX03 *
SN-020905Warning messages might appear when you read a large file from a UNIXfile systemE9BX03 *
SN-030981MP CONNECT (multi-process CONNECT) might fail when you use the XMS Access Method in Base SASŪ in the z/OS environmentE9BX03 *
SN-010972An error occurs when you use the %INCLUDE statement with a fileref that begins with an underscoreE9BX03 *
SN-031411Unused allocated space on a non-last volume of an existing library will put out a warning versus an errorE9BX03 *
E9BC08
SN-030992A memory shortage might cause a loop and SC78 abend to occur in SASŪ Metadata Server in the z/OS environmentE9BX03 *
SN-031147Performance issues might occur with the SASŪ OLAP Server in the z/OS environmentE9BX03 *

E9BX03 * Indicates fixes that are appearing in a bundle for the first time.




Back to the Main Hot Fix Downloads Page


PLEASE CAREFULLY READ THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT ("AGREEMENT") BEFORE DOWNLOADING MATERIALS FROM THIS SITE. BY DOWNLOADING ANY MATERIALS FROM THIS SITE, YOU ARE AGREEING TO THESE TERMS.

You are downloading software code ("Code") which will become part of a product ("Software") you currently have licensed from SAS Institute Inc. or one of its subsidiaries ("the Institute"). this Code is designed to either correct an error in the Software or to add functionality to the Software. The code is governed by the same agreement which governs the Software. If you do not have an existing agreement with the Institute governing the Software, you may not download the Code.

SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. ® indicates USA registration. Other brand and product names are registered tradema rks or trademarks of their respective companies.


Contact Us | Sitemap | www.sas.com | Terms of Use & Legal Information | Privacy Statement
Copyright © 2008 SAS Institute Inc. All Rights Reserved.