In a SAS/CONNECT spawner environment on z/OS, the CLIENTWORK system option does not control the allocation of the SAS WORK data set.

Although CLIENTWORK is documented as a mechanism to control WORK allocation for a SAS/CONNECT server, beginning with SAS^® 9.4M7 (TS1M7), the option has no effect on WORK allocation when you launch the server by the SAS/CONNECT spawner on z/OS.

Impact

When you specify CLIENTWORK, the WORK data set allocation parameters are ignored for spawned SAS/CONNECT server sessions. As a result, sites that rely on CLIENTWORK to manage WORK space characteristics (such as device type or allocation size) might observe unexpected WORK allocation behavior.

Workaround

To control WORK allocation for SAS/CONNECT servers spawned on z/OS, specify standard WORK allocation options instead of CLIENTWORK. 

Here are some examples:

-WORKLARGE
-WORK(CYLS,'2,5')
-WORKDEV(SYSDA)
-WORKDEVCOUNT(2)

Note that you must define these options in one of the following locations:

• the SASRXCFG(REXXSITE) member
• the SPNCPARM member used by the SAS/CONNECT Spawner started task
• the spncshel.sh shell script that launches the SAS/CONNECT server

Ensure that the options are applied in the location that is actually used to start the spawned server.

Currently, a hot fix that restores correct handling of WORK allocation in this environment is not available.