Providing software solutions since 1976
40451 - Enabling the use of authorized TSO commands for SAS® 9.2 spawners in the z/OS operating environment- Problem Note
This note provides setup instructions for enabling the IBM utility tsocmd and applying Hot Fix C17001 for SAS 9.2 (TS2M2) or Hot Fix B25015 for SAS 9.2 (TS2M3).
49598 - MP Connect sessions that use piping via SASESOCK are slower in SAS/CONNECT® software releases later than 9.1.3- Problem Note
MP CONNECT sessions that use piping via SASESOCK may run slower in SAS/CONNECT® software releases greater than SAS®: 9.1.3 than they did in previous releases. There is current no solution or workaround for this ...
49352 - MP CONNECT programs that use SASESOCK pipeline parallelism might not respond because of blocking- Problem Note
Piping has a well known limitation in which a process can write only a finite amount of data to a pipe before the pipe reader consumes some of the data, making room in TCP/IP buffers for more data to be written. The ...
48987 - The SAS /CONNECT® spawner stops responding when a disabled account tries to log on- Problem Note
When you log on to the SAS/CONNECT® spawner with a disabled user account, the spawner stops responding. The spawner should not stop responding, even when a disabled account is used. The problem only occurs in the ...
42312 - An S0C4 abend occurs when implementing LOG4SAS for the SAS/CONNECT® Spawner in a z/OS operating environment- Problem Note
When implementing the LOG4SAS for the SAS/CONNECT Spawner for SAS® 9.2 under z/OS, the spawner task abends with a SEC6 REASON CODE=0000FD0B. A user abend 4095 also occurs in the system messages. In the TKMVSJNL file, ...
The following error messages might occur when running the SAS/CONNECT PC Spawner program for SAS® release 9.2(TS2M3). ERROR: A communication subsystem partner link setup request failure has occurred. ERROR: Cannot ...
ERROR: Windows SSL error -2146893015 (0x80090329) occurred at line 3975. Problem Note 46092: The error "The specified data could not be encrypted" occurs when you use the UPLOAD or DOWNLOAD procedure in SAS/CONNECT ...
4319 - Zap for MP CONNECT on OS/390 to allow renamed SASVXMS load module for SAS 8- Problem Note
The MP CONNECT feature of SAS/CONNECT software requires installing the SASVXMS load module into an authorized load library. This requirement also exists for SAS/SHARE software if you use the Cross Memory Services (XMS) ...
45960 - The SAS/CONNECT® Job Spawner does not release file handles- Problem Note
In Windows operating environments, the SAS Job Spawner does not release file handles after a user logs off the system. Consequently, all handles remain in use and no other users can connect.
45416 - An MP CONNECT signon failure might occur intermittently on Windows Server 2003- Problem Note
On Windows Server 2003 platforms, Multi-Processing (MP) CONNECT sign-ons might fail intermittently because of the way that TCP/IP ephemeral ports are handled. The client error messages do not contain much diagnostic ...
44756 - SAS/CONNECT® spawner for SAS® 9.1.3 on OpenVMS Alpha requires passwords with all uppercase characters- Problem Note
The SAS/CONNECT® spawner on OpenVMS Alpha fails to authenticate users unless their passwords contain only uppercase characters.
44036 - Secure Sockets Layer (SSL) functionality cannot import certificates to a local computer- Problem Note
SSL certificates can be imported only to the personal user's location. If the certificate is imported to the local computer's location, signon attempts to the server fail. For example: When importing certificates, one ...
44505 - Signon to SAS®9 SAS/CONNECT® spawner might fail after you upgrade to z/OS 1.12 or later- Problem Note
Errors on the client side:<br /> ERROR: A communication subsystem partner link setup request failure has occurred.<br / ERROR: TCP link establishment failed. <br /> ERROR: Remote signon to MVSHOST.SPAWNER913 canceled. ...
When you submit SAS Scalable Performance Data (SPD) Server LIBNAME statements from SAS Enterprise Guide to a SAS grid, the libraries are not available in SAS Enterprise Guide under /Server List/SASApp/Library. Click ...
44185 - An error occurs when you try to assign a DBMS library in the SAS® Enterprise Guide® library tree- Problem Note
The DBMS library does not show up in the SAS® Enterprise Guide® library tree.
In SAS/CONNECT® software, when you specify a SAS view in the DATA= option of the UPLOAD and DOWNLOAD procedures, the software adds null values to the end of a variable. If you open the file that is created by this ...
43664 - The TERMSTMT= option terminates a job after 30 seconds- Problem Note
If the client in a SAS/CONNECT® session in SAS® 9.2, the TERMSTMT option terminates a job after 30 seconds
42437 - Errors occur when you use SAS/CONNECT® software to sign on to a UNIX environment that is configured with SSH- Problem Note
When you use the SIGNON command to connect to a UNIX machine that is configured with the SSH protocol, an error occurs: Cannot read TCP socket, system message is
42492 - An error occurs when you use the DATECOPY option in the DOWNLOAD or UPLOAD procedures- Problem Note
The SAS/CONNECT® UPLOAD/DOWNLOAD procedure requires that the DATECOPY option appear in a specific order
42252 - DATA step views are not accessible when you submit and pass them to a SAS grid from SAS® Enterprise Guide®- Problem Note
In SAS Enterprise Guide, when you submit a DATA step view that references a fileref and pass it to a SAS grid, that view cannot be accessed. The problem occurs because the fileref is not forwarded from the grid to the ...
When doing an Action C installation, the samples (SPNCNTL & SPNCSHEL) for the z/OS SAS/CONNECT spawner in the prefix.BAMISC are incorrect.
41468 - Multi-processing CONNECT programs might become unresponsive when data is piped using the SASESOCK engine- Problem Note
Multi-processing CONNECT programs might become unresponsive when data is piped using the SASESOCK engine.
A batch SAS/CONNECT SIGNON statement that is submitted using PW=_PROMPT_ does not prompt for passwords, even if a terminal is available for the prompt. The following sample code prompts for your password when it is ...
40926 - A configuration failure error for the SAS® Metadata Server might occur during a planned installation of SAS® 9.2- Problem Note
During a planned installation of SAS® 9.2, a configuration failure error might occur. The error indicates that the SAS® Metadata Server could not be started and configured.
In SAS/CONNECT software, when you download or upload a file that contains special characters such as parentheses in the filename and are using the INFILE= system option with a wildcard, the filename is truncated ...
