 |
||
|
||
|
||
|
Return to 9.1.3 DBCS Hot Fix Home | |
|
||
What's New?
| Hot Fix Releases for the Week of: November 16, 2009 |
| E9BD16 for BASE SAS | ||
| Issue(s) Addressed: | Introduced: | |
| SN-017147 | Output to RECFM=FB SASLIST file may contain carriage control | E9BA11 |
| SN-017380 | Client TSO session loops while processing FSBROWSE on library allocated to a SAS/SHARE® server | E9BA11 |
| SN-019281 | PROC CIMPORT fails when the transport file is a member of an uncataloged partitioned data set | E9BA41 |
| SN-017797 | "ERROR: Physical file does not exist, SYS06144.T115731.RA000.N389610T.INCL.H04" message from %INCLUDE | E9BA41 |
| SN-013425 | Autoexec may continue processing when leaving MENU entry defined to SHARE server in SAS/AF | E9BA52 |
| SN-018423 | Control incorrectly appears to return to SAS/AF® application when sorting data on the mainframe | E9BA52 |
| SN-013720 | TSO may hang when leaving SAS after running SAS/AF application with SAS/SHARE | E9BA52 |
| SN-016476 | System abend 0C4 in module SASTK | E9BA52 |
| SN-018430 | ERROR: Unable to initialize TCP/IP subsystem returns Condition Code 0 | E9BA52 |
| SN-019299 | Division-by-zero processing causes severe performance degradation | E9BA75 |
| SN-020327 | Contents of a variable change when you pass the variable to the FILEEXIST function | E9BB03 |
| SN-018637 | ALTLOG and ALTLIST files may be missing if directed to HFS | E9BB03 |
| SN-019065 | DISP is ignored in LIBNAME statement when existing allocation already exists | E9BB03 |
| SN-019522 | The FILENAME function for an HFS pathSAS argument generates incorrect results | E9BB03 |
| SN-017038 | Limited support in SAS® 9.1.3 SP4 for DSNTYPE=LARGE data sets when running under z/OS Releases V1R7 and later | E9BB25 |
| SN-019842 | SAS® 9 software reads all generations of a generation data group controlled by the Storage Management Subsystem | E9BB25 |
| SN-020035 | The RELEASE procedure can damage a currently assigned SAS® data library, resulting in an I/O error or U315 abnormal ending message | E9BB34 |
| SN-020459 | Performance issues found in SAS® software memory management on the z/OS platform | E9BB44 |
| SN-020583 | Concatenation of 257 physical sequential data sets fails when you run SAS® software on z/OS | E9BB57 |
| SN-020905 | Warning messages might appear when you read a large file from a UNIX file system | E9BB67 |
| SN-030981 | MP CONNECT (multi-process CONNECT) might fail when you use the XMS Access Method in Base SAS® in the z/OS environment | E9BB90 |
| SN-010972 | An error occurs when you use the %INCLUDE statement with a fileref that begins with an underscore | E9BC06 |
| SN-031411 | Unused allocated space on a volume other than the last volume of an existing library will generate a warning rather than an error | E9BC06 |
| SN-033865 | Base SAS® software might enter a loop after an input/output (I/O) error or “out of space” error occurs | E9BC53 |
| SN-032798 | The system ends abnormally with an S0C4 abend code during SAS termination | E9BC53 |
| SN-033040 | A %INCLUDE statement for an explicit path of a cataloged disk data set might fail in Base SAS® in the z/OS environment | E9BC53 |
| SN-034459 | Using the NODLTRUNCK option to process truncated libraries can result in data loss | E9BC64 |
| SN-033892 | A SAS/SHARE® server does not free a library when a client times out | E9BC70 |
| SN-035332 | The message "Libname libref is not assigned" might appear if you do not specify an engine | E9BC82 |
| SN-035116 | An error might occur when using ODS on the z/OS operating system after application of hot fix E9BC53 or E9BC70 | E9BC82 |
| SN-035225 | An error might occur when using ODS on the z/OS operating system after application of hot fix E9BC53 or E9BC70 | E9BC82 |
| SN-036164 | ERROR: "Library data set temp.dataset.name does not comply with RECFM=FS requirements or is truncated" | E9BD04 |
| SN-037166 | A user 1319 abend occurs if you specify a FILENAME, INFILE, or FILE user exit when you create a DATA step view | E9BD16 |
| Select an Available Operating System: | ||
| MAINFRAME: | z/OS_(OS/390) | |
|
| Top ^ |
| E9BD18 for BASE SAS | ||
| Issue(s) Addressed: | Introduced: | |
| SN-037898 | Use of 2GB or more of memory by PROC TRANSPOSE can produce incorrect results | E9BD18 |
| Select an Available Operating System: | ||
| UNIX: | HPUX, Solaris_(64-bit), AIX, Linux, HPUX_for_Itanium, Linux_for_Itanium, Solaris_for_x64 | |
|
| Top ^ |
| Hot Fix Releases for the Week of: November 9, 2009 |
| E9OR04 for SAS/OR | ||
| Issue(s) Addressed: | Introduced: | |
| SN-036896 | An incorrect optimum is produced during credit risk mitigant allocation | E9OR04 |
| Select an Available Operating System: | ||
| PC: | Windows, Windows_for_IPF_(64_bit) | |
| UNIX: | HPUX, Solaris_(64-bit), AIX, Tru_64, Linux, HPUX_for_Itanium, Linux_for_Itanium | |
|
| Top ^ |
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.