11-19-2016 07:18 AM
Many times, we are getting exit code 102 in platform lsf v9.1 on SAS 9.4 grid env. It does not repeat for few jobs (when run on next day) but is persistent for other jobs.
Could I please get help to resolve this issue.
11-19-2016 05:31 PM
I suggest that this type of problem is best progressed with SAS Tech Support if you haven't done so already. From my own experience LSF errors are tricky to diagnose.
11-19-2016 09:16 PM
11-21-2016 03:39 AM
this not is not directly related to your issue, but it should be able to give you and SAS Technical Suppport additional insight than a plain exit code 102.
Problem Note 50749: Submitting a SAS® job to a SAS® grid environment might fail with the error "Could not Start Grid Job": http://support.sas.com/kb/50/749.html
3 weeks ago - last edited 3 weeks ago
When sasgsub returns an RC=102, chances are that you are trying to run it with the -GRIDSASOPTS parameter to pass in values to the sas program that you're trying to execute.
Here is the correct syntax for that:
sasgsub -GRIDSUBMITPGM ~/test.sas -GRIDSASOPTS "(-sysparm "arg1")" -GRIDWAITRESULTS -GRIDWORK /sas/gridwork
Note the double quoting around the brackets then again around the actual argument.
You probably were trying to use a variation like one of the ones below, which do NOT work and will give you the sasgsub/lsf RC=102 exit code.
sasgsub -GRIDSUBMITPGM ~/test.sas -GRIDSASOPTS "(sysparm arg1)" -GRIDWAITRESULTS -GRIDWORK /sas/gridwork
sasgsub -GRIDSUBMITPGM ~/test.sas -GRIDSASOPTS 'sysparm arg1' -GRIDWAITRESULTS -GRIDWORK /sas/gridwork
sasgsub -GRIDSUBMITPGM ~/test.sas -GRIDSASOPTS "sysparm arg1" -GRIDWAITRESULTS -GRIDWORK /sas/gridwork