CLIENTWORK System Option: z/OS

Specifies dynamic allocation options for creating client work libraries in a SAS server environment.

Valid in:	Configuration file, SAS invocation
Category:	File Control: SASFILES
PROC OPTIONS GROUP=	SASFILES
Default:	null
z/OS specifics:	All

Syntax

Details

Syntax

CLIENTWORK=“operand ... <operand ...>”

Required Argument

The required operands can be one of the following TSO ALLOCATE command operands:

operand

can be one of the following operands. You must specify all of these operands.

UNIT(device type)
TRACKS, CYL, BLOCK()
SPACE(primary<,secondary>)

Optional Argument

The optional operands can be one of the following TSO ALLOCATE commands:

operand

can be any of the following operands. You can specify one or more of these operands.

UCOUNT(<number of devices>)
VOL(volser<,volser...>)
STORCLAS(storage class
MGMTCLAS(management class)
DATACLAS(data class)
DSNTYPE(LARGE)

Details

The CLIENTWORK option specifies the data set dynamic allocation options that a SAS server attempts to use when it creates a temporary work library for a client session. The CLIENTWORK option is used only when the server’s WORK library resides in a direct access bound library. The CLIENTWORK option has no effect when the server’s WORK library resides in a UFS directory. For more information, see WORK Library and Other Utility Files.

The operands in the preceding list have the same syntax and meaning as when they are specified on the TSO ALLOCATE command. For more information, see the IBM documentation about the ALLOCATE command. However, the CLIENTWORK option does not depend on TSO services. CLIENTWORK can be specified in any execution environment supported by SAS, including batch, started task, and USS shell.

If the server’s WORK library resides in a direct access bound library, the SAS server dynamically allocates a temporary MVS data set for each client that connects to the server. If CLIENTWORK is specified, then its operands are used to determine the allocation. This data set contains the work library for the client. It is created with a unique system-generated name.

If any of the following three conditions are true, then the SAS server reverts to the behavior that is described for the case in which CLIENTWORK is null:

CLIENTWORK is not specified.
CLIENTWORK is specified with a value of NULL.
The CLIENTWORK operands refer to resources (for example, a non-existent SMS data class) that are not defined on the z/OS system.

If the value that is specified for CLIENTWORK is null, then the size of the client WORK library is governed by the values of the following SAS system options that are in effect for the initialization of the SAS server:

FILESPPRI

primary space allocation

FILESPSEC

secondary space allocation

FILEUNIT

unit of space

Note:

The CLIENTWORK option provides the advantage of enabling a SAS server to create client work libraries that can span multiple volumes.
The temporary data sets that are created for client work libraries must be regular-format sequential data sets. Extended-format sequential data sets are not supported. Therefore, for the DATACLAS operand, do not specify a data class with a data set name type of extended.
The processing for the CLIENTWORK option is identical to that for the UTILLOC option with the exception that the ALLOC command name is not specified as part of CLIENTWORK. For more information, see UTILLOC= System Option: z/OS.