Problem Note 16738: SASĀ® 9.1 IOM and CONNECT Spawner sessions fail with security violations
under z/OS 1.7
Under z/OS 1.7, a problem has been found in the USS TSO command
services environment. IBM's FOMFTSO routine modified the allocation of
SYSTSPRT to allow the use of TSOOUT. If an alternate path is not
specified, the default path is set to /dev/fd1. This results
in a security violation reported in the system log file. The
SAS/CONNECT Spawner log displays the process ending but no messages are
produced.
A work around to this problem is to insert the following into the shell
script which launches the Server task:
export tsoout=
This environment variable setting must be placed prior to the EXEC
statement. This environment variable is case sensitive. The syntax
as shown above is correct.
JES3 sites have reported seeing a S0C4 in USETSOENV in the
sysout file associated with the USS process.
NOTE: The below fix for this problem is a source fix which is the same as
as the workaround. If this issue affects an existing Spawner setup, the
workaround is the recommended way to correct the issue. If you apply
the hotfix to correct the issue, you will need to go through
the Spawner setup concerning picking up the "fixed" USS shell
script.
Select the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS/CONNECT | z/OS | 9.1 TS1M0 | 9.1 TS1M3 SP4 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | high |
Topic: | Software Components ==> Connect Spawner
|
Date Modified: | 2007-07-26 11:34:54 |
Date Created: | 2005-12-23 11:23:34 |