Problem Note 62831: Grid jobs fail with exit code 255 if they are set to deliver a dispatch notification in Microsoft Windows
In IBM Spectrum LSF 10.1, an issue exists in which jobs fail immediately with exit code 255. This issue occurs with both scheduled and non-scheduled jobs. You encounter this issue under the following conditions:
- You submit a non-scheduled job using the -B option with bsub.exe.
- You use the job start notification and scheduling with Process Manager.
Note: Jobs that are set to send a notification at the end of the job (using the -N option with bsub.exe) work as expected.
There are several workarounds for this issue.
For scheduled jobs, choose one of the following workarounds:
- Connect the notifications to the flow rather than to the job.
- Ensure that the job is set to notify only when the job ends by following these instructions:
- In SAS® Management Console, select Schedule Manager ► flow-name.
- Right-click the job name and select Properties.
- On the Scheduling Details tab, click Advanced.
- On the General tab in the Email Notification section, select the Notify when job check box. In the drop-down menu to the right of the check box, select ends as shown in the image below:
For non-scheduled jobs, use the notification for the end of job (using the -N option with bsub.exe).
Click the Downloads tab for a link to a download that fixes this issue.
Operating System and Release Information
SAS System | Platform LSF | Microsoft® Windows® for x64 | 10.1 | | 9.4 TS1M5 | |
Microsoft Windows 8 Enterprise 32-bit | 10.1 | | 9.4 TS1M5 | |
Microsoft Windows 8 Enterprise x64 | 10.1 | | 9.4 TS1M5 | |
Microsoft Windows 8 Pro 32-bit | 10.1 | | 9.4 TS1M5 | |
Microsoft Windows 8 Pro x64 | 10.1 | | 9.4 TS1M5 | |
Microsoft Windows 8.1 Enterprise 32-bit | 10.1 | | 9.4 TS1M5 | |
Microsoft Windows 8.1 Enterprise x64 | 10.1 | | 9.4 TS1M5 | |
Microsoft Windows 8.1 Pro 32-bit | 10.1 | | 9.4 TS1M5 | |
Microsoft Windows 8.1 Pro x64 | 10.1 | | 9.4 TS1M5 | |
Microsoft Windows 10 | 10.1 | | 9.4 TS1M5 | |
Microsoft Windows Server 2008 | 10.1 | | 9.4 TS1M5 | |
Microsoft Windows Server 2008 R2 | 10.1 | | 9.4 TS1M5 | |
Microsoft Windows Server 2008 for x64 | 10.1 | | 9.4 TS1M5 | |
Microsoft Windows Server 2012 Datacenter | 10.1 | | 9.4 TS1M5 | |
Microsoft Windows Server 2012 R2 Datacenter | 10.1 | | 9.4 TS1M5 | |
Microsoft Windows Server 2012 R2 Std | 10.1 | | 9.4 TS1M5 | |
Microsoft Windows Server 2012 Std | 10.1 | | 9.4 TS1M5 | |
Microsoft Windows Server 2016 | 10.1 | | 9.4 TS1M5 | |
Windows 7 Enterprise 32 bit | 10.1 | | 9.4 TS1M5 | |
Windows 7 Enterprise x64 | 10.1 | | 9.4 TS1M5 | |
Windows 7 Home Premium 32 bit | 10.1 | | 9.4 TS1M5 | |
Windows 7 Home Premium x64 | 10.1 | | 9.4 TS1M5 | |
Windows 7 Professional 32 bit | 10.1 | | 9.4 TS1M5 | |
Windows 7 Professional x64 | 10.1 | | 9.4 TS1M5 | |
Windows 7 Ultimate 32 bit | 10.1 | | 9.4 TS1M5 | |
Windows 7 Ultimate x64 | 10.1 | | 9.4 TS1M5 | |
*
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.
Both scheduled and non-scheduled grid jobs can fail with exit code 255 if they are set to deliver a notification at the start of the job.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2018-08-29 13:19:20 |
Date Created: | 2018-08-28 11:01:29 |