With some relatively simple changes, you can use SAS checkpoint/restart capability with scheduled SAS jobs so that they are automatically re-queued and re-run by Platform LSF.

First, you need to set acceptable exit codes, in SAS, to indicate that the SAS job can be re-queued and re-run. These are exit codes for which you want to re-submit the job automatically so that it restarts from where it stopped rather than rerunning all of the code. You can enter multiple exit codes on the REQUEUE_EXIT_VALUES parameter line, separated by spaces. However, you should not define 1 as one of the exit codes. That number is used typically as the code to indicate when SAS completes a task with warnings (but with no errors).

After you assign the exit codes, you need to set up a specific LSF queue to which to submit your checkpoint/restart jobs. To do this, modify you Platform LSF lsb.queues file by adding a new queue definition similar to the following, but one that contains your specific, re-runnable exit codes:

After you modify your lsb.queues file, you need to indicate that Platform LSF should re-read the configuration files. To do that, either restart Platform LSF or run the following commands as the primary LSF administrative user:

With the LSF queue now set up, you need to configure your SAS batch server so that it adds the proper SAS checkpoint/restart options at start-up. To do this, you need to add some code to either the sasbatch_usermods.bat file )for Microsoft Windows) or the sasbatch_usermods.sh script file (for UNIX), both of which reside under your application server's BatchServer folder or directory.

For Windows operating environments:

The sasbatch_usermods.bat file typically resides in configuration-directory\Lev1\SASApp\BatchServer. Append the following code to the sasbatch_usermods.bat file:

For UNIX operating environments:

For all of these steps to work, you need to indicate that SAS and Platform Process Manager should submit the job in the flow to the designated restart queue. You do this before scheduling the flow by opening the properties of the job in the flow that should run in the restart queue using the above checkpoint restart options. In the job properties window:

1. Click the Scheduling Details tab.
2. Click the Advanced button and log on to Process Manager.
3. In the resulting Advanced Properties window, click the Submit tab. Then select the proper queue from the Submit to queue(s) list, as shown in the following display:

   
   
   

   Operating System and Release Information

   Product Family	Product	System	SAS Release
   			Reported	Fixed*
   SAS System	Platform Process Manager	Microsoft® Windows® for x64	9.3 TS1M2
   		Microsoft Windows Server 2003 Datacenter Edition	9.3 TS1M2
   		Microsoft Windows Server 2003 Enterprise Edition	9.3 TS1M2
   		Microsoft Windows Server 2003 Standard Edition	9.3 TS1M2
   		Microsoft Windows Server 2003 for x64	9.3 TS1M2
   		Microsoft Windows Server 2008	9.3 TS1M2
   		Microsoft Windows Server 2008 R2 for x64	9.3 TS1M2
   		Microsoft Windows Server 2008 for x64	9.3 TS1M2
   		Microsoft Windows XP Professional	9.3 TS1M2
   		Windows 7 Enterprise 32 bit	9.3 TS1M2
   		Windows 7 Enterprise x64	9.3 TS1M2
   		Windows 7 Home Premium 32 bit	9.3 TS1M2
   		Windows 7 Home Premium x64	9.3 TS1M2
   		Windows 7 Professional 32 bit	9.3 TS1M2
   		Windows 7 Professional x64	9.3 TS1M2
   		Windows 7 Ultimate 32 bit	9.3 TS1M2
   		Windows 7 Ultimate x64	9.3 TS1M2
   		Windows Vista	9.3 TS1M2
   		Windows Vista for x64	9.3 TS1M2
   		64-bit Enabled AIX	9.3 TS1M2
   		64-bit Enabled HP-UX	9.3 TS1M2
   		64-bit Enabled Solaris	9.3 TS1M2
   		HP-UX IPF	9.3 TS1M2
   		Linux	9.3 TS1M2
   		Linux for x64	9.3 TS1M2
   		Solaris for x64	9.3 TS1M2

   * 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.