Time-outs in SAS^® spawned servers, especially the SAS^® Workspace Server and SAS/CONNECT^® Servers, are controlled by the JWT value that is set in the SMFPRMxx member of SYS1.PARMLIB.

For example, if the JWT value is set to 20 minutes, and a SAS Workspace Server is left idle for more than 20 minutes, then the workspace server abends with a system 522 abend. Note that this limit also applies to the SAS^® Stored Process Server, but by default it wakes up every 15 minutes to do cleanup. Therefore, unless the JWT is set to 15 minutes or less, the SAS Stored Process Server should not time out.

You can avoid such time-outs in one of three ways:

• Disable the JWT completely for all USS processes by setting the MAXCPUTIME parameter to 86400 in 'SYS1.PARMLIB'. (This is much the same as setting TIME=1440 in JCL.)
• Disable the JWT completely for a particular user by setting the OMVS CPUTIMEMAX value to 86400 in the user’s RACF OMVS segment. (Again, much the same as setting TIME=1440 in JCL.) You set the value in the RACF OMVS segment as follows:
ALTUSER user-id OMVS(CPUTIMEMAX(86400))
• Use the z/OS system IEFUTL exit to extend the wait time. This is a more flexible way to avoid time-outs. If IEFUTL needs to uniquely identify these SAS processes, then you have at least two choices for setting the account information:
• You can set the accounting information in the shell script that starts the server using the _BPX_ACCT_DATA environment variable:
export _bpx_acct_data=sasws1

This setting makes the accounting information available to the IEFUTL exit.
• You can set the accounting information about an individual basis, as shown in the following RACF command:
altuser user-id workattr(waaccnt(sasws1))

Alternatively, you can customize the IEFUTL exit so that time is extended differently based on the time of day. For example, you might extend the time more during non-primetime hours.

Operating System and Release Information