topic Re: SAS Jobs Submitted to a Queue directly goes to Exit state in Administration and Deployment

SAS Jobs Submitted to a Queue directly goes to Exit state

Madhan_cog1 — Mon, 28 Dec 2020 12:55:55 GMT

Hi All,

We have installed and configured SAS 9.4 M5 Grid(Multi tier architecture) in a Linux Environment.

We have installed Application server on the Grid control server and only configured Object spawner and SAS EVM agent on the grid nodes.

Completed all the steps required for Load balancing as well.

Now we have defined three queues.

Normal- To execute on grid control server.

Big-To execute on grid node2

Big_priority-To execute on grid node3.

When we submit the jobs in normal queue the job gets completed succesfully.

But when we submit jobs to other two queues the job gets submitted to corresponding hosts but it directly goes to EXIT state.

When we checked the job id we found below.

[scesasdemo@scevalremote1 SASGSUB-2020-12-28_13.44.54.810_test]$ bhist -l 2210
\
Job <2210>, Job Name <test>, User <scesasdemo>, Project <default>, Command </sh
ared/sas/config/Lev2/SASApp/GridServer/sasgrid "SASBATCHSA
SPGM:'test.sas'" SASWANTJOBINFO:1 "SASBATCHWRKDIR:'/gridwo
rk/work/scesasdemo/SASGSUB-2020-12-28_13.44.54.810_test'">
Mon Dec 28 13:44:54: Submitted from host <scevalremote1.corp.novocorp.net>, to
Queue <big>, CWD <$HOME>, Requested Resources <SASApp>;
Mon Dec 28 13:44:55: Dispatched 1 Task(s) on Host(s) <scevalgrid3.corp.novocorp
.net>, Allocated 1 Slot(s) on Host(s) <scevalgrid3.corp.no
vocorp.net>, Effective RES_REQ <select[(SASApp) && (type =
= any)] order[r15s:pg] >;
Mon Dec 28 13:44:56: Starting (Pid 4042);
Mon Dec 28 13:44:56: Running with execution home </nnhome/scesasdemo>, Executio
n CWD </nnhome/scesasdemo>, Execution Pid <4042>;
Mon Dec 28 13:44:56: Exited with exit code 112. The CPU time used is 0.2 second
s;
Mon Dec 28 13:44:56: Completed <exit>;

Summary of time in seconds spent in various states by Mon Dec 28 13:44:56
PEND PSUSP RUN USUSP SSUSP UNKWN TOTAL
1 0 1 0 0 0 2

Job exited with code 112.

Could you please suggest what could be the issue.

Thanks,

Madhan M.

Re: SAS Jobs Submitted to a Queue directly goes to Exit state

AnandVyas — Mon, 28 Dec 2020 13:18:59 GMT

Hi @Madhan_cog1

Are you able to submit jobs directly using bsub to this particular queue/node and see if it works successfully?

bsub -q "big" sleep 300

If it works fine then LSF is working as expected, there is some issue with launch of SAS Session on the particular node. Here is a snap from LSF KB page as well:

Exit codes less than 128 relate to application exit values, while exit codes greater than 128 relate to system signal exit values (LSF adds 128 to system values)

Reference: https://www.ibm.com/support/knowledgecenter/SSWRJV_10.1.0/lsf_admin/job_exit_codes_lsf.html

In order to troubleshoot further on SAS Side, check if user has the permissions to submit job to this queue, connect spawner is running on the node or check for object spawner logs.

Re: SAS Jobs Submitted to a Queue directly goes to Exit state

Madhan_cog1 — Mon, 28 Dec 2020 13:32:46 GMT

Hi Anand,

Thanks for the response.

Yes -

bsub -q "big" sleep 300

This is working.

Object spawner on the grid nodes are running.

We could see the below in the log.

2020-12-28T12:04:36,932 INFO [00000063] :scesas - Attempt to connect to peer iom://scevalgrid2.corp.novocorp.net:8582;;noredirect,classfactory=6A829631-BE4A-4CFF-82F6-B378705DF34C,user=,encr=SASProprietary,encrlvl=credentials/ for cluster SASApp - Logical Workspace Server (A5HKFV4Z.AW000006) failed with exception <?xml version="1.0" ?><Exceptions><Exception><SASMessage severity="Error">A connection refused usually indicates the target server is not active. Or, if active, it may be listening on a different port or service.</SASMessage></Exception><Exception><SASMessage severity="Error">The Bridge Protocol Engine Socket Access Method was unable to connect to host scevalgrid2.corp.novocorp.net, port 8582.</SASMessage></Exception><Exception><SASMessage severity="Error">The TCP/IP tcpSockConnect() support routine failed with error 111 (The connection was refused.).</SASMessage></Exception></Exceptions>.
2020-12-28T12:04:36,932 INFO [00000062] :scesas - Attempt to connect to peer iom://scevalgrid3.corp.novocorp.net:8582;;noredirect,classfactory=6A829631-BE4A-4CFF-82F6-B378705DF34C,user=,encr=SASProprietary,encrlvl=credentials/ for cluster SASApp - Logical Workspace Server (A5HKFV4Z.AW000006) failed with exception <?xml version="1.0" ?><Exceptions><Exception><SASMessage severity="Error">A connection refused usually indicates the target server is not active. Or, if active, it may be listening on a different port or service.</SASMessage></Exception><Exception><SASMessage severity="Error">The Bridge Protocol Engine Socket Access Method was unable to connect to host scevalgrid3.corp.novocorp.net, port 8582.</SASMessage></Exception><Exception><SASMessage severity="Error">The TCP/IP tcpSockConnect() support routine failed with error 111 (The connection was refused.).</SASMessage></Exception></Exceptions>.

Thanks,

Madhan M.

Re: SAS Jobs Submitted to a Queue directly goes to Exit state

AnandVyas — Mon, 28 Dec 2020 13:41:42 GMT

Is your grid configured to support HA for object spawner? Does all the machines run object spawner service? I can see connection refused messages in the log you have shared.

Did the configuration work without errors before making the changes to the queue?

Re: SAS Jobs Submitted to a Queue directly goes to Exit state

doug_sas — Mon, 28 Dec 2020 15:36:42 GMT

SASGSUB just runs SAS without using the object spawner. The 112 indicates something is wrong with the setup on the grid node. See if there is a SasGrid.*.log in the <config>/LevX/<AppServer>/GridServer/Logs subdirectory on the execution machine. That log may have the SAS error message for the 112 error code.

You could also run the command that LSF ran on the execution machine Fromm terminal window and see what happens.

Re: SAS Jobs Submitted to a Queue directly goes to Exit state

Madhan_cog1 — Tue, 29 Dec 2020 05:51:48 GMT

Hi Juan,

Thanks for the response.

Yes we have logs under <config>/LevX/<AppServer>/GridServer/Logs.

The log shows like below.

SASGRID: Job started at 11:29:49 on 12/28/20
SASGRID: parm as entered = SASBATCHSASPGM:'test.sas'
SASGRID: parm stripped = SASBATCHSASPGM:'test.sas'
SASGRID: name = SASBATCHSASPGM
SASGRID: value = 'test.sas'
SASGRID: parm as entered = SASWANTJOBINFO:1
SASGRID: parm stripped = SASWANTJOBINFO:1
SASGRID: name = SASWANTJOBINFO
SASGRID: value = 1
SASGRID: parm as entered = SASBATCHWRKDIR:'/gridwork/work/scesasdemo/SASGSUB-2020-12-28_08.28.34.156_test'
SASGRID: parm stripped = SASBATCHWRKDIR:'/gridwork/work/scesasdemo/SASGSUB-2020-12-28_08.28.34.156_test'
SASGRID: name = SASBATCHWRKDIR
SASGRID: value = '/gridwork/work/scesasdemo/SASGSUB-2020-12-28_08.28.34.156_test'
SASGRID: envVars ***=== START ===***
APPSERVER_ROOT=/shared/sas/config/Lev2/SASApp
BASESASDIR=/shared/sas/apps/SASHome/SASFoundation/9.4
BASH=/bin/sh
BASHOPTS=cmdhist:extquote:force_fignore:hostcomplete:interactive_comments:progcomp:promptvars:sourcepath
BASH_ALIASES=()
BASH_ARGC=([0]="3")
BASH_ARGV=([0]="SASBATCHWRKDIR:'/gridwork/work/scesasdemo/SASGSUB-2020-12-28_08.28.34.156_test'" [1]="SASWANTJOBINFO:1" [2]="SASBATCHSASPGM:'test.sas'")
BASH_CMDS=()
BASH_LINENO=([0]="0")
BASH_SOURCE=([0]="/shared/sas/config/Lev2/SASApp/GridServer/sasgrid")
BASH_VERSINFO=([0]="4" [1]="2" [2]="46" [3]="2" [4]="release" [5]="x86_64-redhat-linux-gnu")
BASH_VERSION='4.2.46(2)-release'
BINARY_TYPE_HPC=
BSUB_BLOCK_EXEC_HOST=
CONTEXT_USERMODS_OPTIONS=
DEPLOYWIZ=/shared/sas/apps/SASHome/SASDeploymentManager/9.4/products/deploywiz__94512__prt__xx__sp0__1/deploywiz
DIRSTACK=()
EUID=634867
GROUPS=()
HISTCONTROL=ignoredups
HISTSIZE=1000
HOME=/nnhome/scesasdemo
HOST=scevalremote1
HOSTNAME=scevalgrid3.corp.novocorp.net
HOSTTYPE=X86_64
IFS='
'
INHERIT=0
JAVA_HOME=/shared/sas/apps/SASHome/SASPrivateJavaRuntimeEnvironment/9.4/jre
JAVA_JRE_COMMAND=/shared/sas/apps/SASHome/SASPrivateJavaRuntimeEnvironment/9.4/jre/bin/java
JOB_TERMINATE_INTERVAL=10
JS_ARCH=linux2.6-glibc2.3-x86_64
JS_ENVDIR=/shared/pm/conf
JS_HOME=/shared/pm
JS_SERVERDIR=/shared/pm/10.1/linux2.6-glibc2.3-x86_64/etc
JS_VERSION=10.1
KRB5CCNAME=KEYRING:persistent:634867
LANG=en_US.UTF-8
LD_LIBRARY_PATH=/shared/sas/apps/SASHome/Secure/sasexe:/shared/lsf/10.1/linux2.6-glibc2.3-x86_64/lib:/shared/sas/apps/SASHome/Secure/sasexe:/shared/sas/apps/SASHome/SASPrivateJavaRuntimeEnvironment/9.4/jre/lib/i386/server:/shared/sas/apps/SASHome/SASPrivateJavaRuntimeEnvironment/9.4/jre/lib/i386:/shared/sas/apps/SASHome/SASFoundation/9.4/sasexe:/shared/pm/10.1/linux2.6-glibc2.3-x86_64/lib:/opt/oracle/product/19.0.0/client_1/lib:/lib:/usr/lib
LESSOPEN='||/usr/bin/lesspipe.sh %s'
LEVEL_ROOT=/shared/sas/config/Lev2
LOGNAME=scesasdemo
LSB_ACCT_FILE=/tmp/2097.tmpdir/.1609140514.2097.acct
LSB_AFFINITY_HOSTFILE=/nnhome/scesasdemo/.lsbatch/1609140514.2097.hostAffinityFile
LSB_BATCH_JID=2097
LSB_CHKFILENAME=/nnhome/scesasdemo/.lsbatch/1609140514.2097
LSB_DJOB_HOSTFILE=/nnhome/scesasdemo/.lsbatch/1609140514.2097.hostfile
LSB_DJOB_NUMPROC=1
LSB_DJOB_RANKFILE=/nnhome/scesasdemo/.lsbatch/1609140514.2097.hostfile
LSB_EEXEC_REAL_GID=
LSB_EEXEC_REAL_UID=
LSB_EFFECTIVE_RSRCREQ='select[(SASApp) && (type == any)] order[r15s:pg] '
LSB_EXEC_CLUSTER=sas_val_cluster
LSB_EXEC_HOSTTYPE=X86_64
LSB_EXIT_PRE_ABORT=99
LSB_HOSTS=scevalgrid3.corp.novocorp.net
LSB_JOBEXIT_STAT=0
LSB_JOBFILENAME=/nnhome/scesasdemo/.lsbatch/1609140514.2097
LSB_JOBID=2097
LSB_JOBINDEX=0
LSB_JOBNAME=test
LSB_JOBRES_CALLBACK=56425@scevalgrid3.corp.novocorp.net
LSB_JOBRES_PID=18631
LSB_JOB_EXECUSER=scesasdemo
LSB_MAX_NUM_PROCESSORS=1
LSB_MCPU_HOSTS='scevalgrid3.corp.novocorp.net 1 '
LSB_OUTDIR=/nnhome/scesasdemo
LSB_PROJECT_NAME=default
LSB_QUEUE=big_priority
LSB_RES_GET_FANOUT_INFO=Y
LSB_SUB_HOST=scevalremote1.corp.novocorp.net
LSB_SUB_RES_REQ=SASApp
LSB_SUB_USER=scesasdemo
LSB_TRAPSIGS='trap # 15 10 12 2 1'
LSB_UNIXGROUP_INT=sasadm
LSB_XFER_OP=
LSFUSER=scesasdemo
LSF_BINDIR=/shared/lsf/10.1/linux2.6-glibc2.3-x86_64/bin
LSF_CGROUP_TOPDIR_KEY=sas_val_cluster
LSF_EGO_ENVDIR=/shared/lsf/conf/ego/sas_val_cluster/kernel
LSF_ENVDIR=/shared/lsf/conf
LSF_FULL_VERSION=10.1
LSF_ISV_MODE=SAS
LSF_ISV_MSG='>;7=736?<;24<=>>@<683?:?1?13=925><1>126:517316;34>;6><?7<7137:>;'
LSF_JOB_TIMESTAMP_VALUE=1609151388
LSF_LIBDIR=/shared/lsf/10.1/linux2.6-glibc2.3-x86_64/lib
LSF_LIM_API_NTRIES=1
LSF_LOGDIR=/shared/lsf/log
LSF_PM_SOCKFD=12
LSF_SERVERDIR=/shared/lsf/10.1/linux2.6-glibc2.3-x86_64/etc
LSNULFILE=/dev/null
LS_COLORS='rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=01;05;37;41:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.axv=01;35:*.anx=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=01;36:*.au=01;36:*.flac=01;36:*.mid=01;36:*.midi=01;36:*.mka=01;36:*.mp3=01;36:*.mpc=01;36:*.ogg=01;36:*.ra=01;36:*.wav=01;36:*.axa=01;36:*.oga=01;36:*.spx=01;36:*.xspf=01;36:'
LS_EXECCWD=/nnhome/scesasdemo/
LS_EXEC_T=START
LS_JOBPID=18631
LS_SUBCWD=/nnhome/scesasdemo/
MACHTYPE=x86_64-redhat-linux-gnu
MAIL=/var/spool/mail/scesasdemo
MANPATH=/shared/pm/10.1/man:/shared/lsf/10.1/man:
OLDPWD=/nnhome/scesasdemo
OPTERR=1
OPTIND=1
ORACLE_BASE=/opt/oracle/product
ORACLE_HOME=/opt/oracle/product/19.0.0/client_1
ORACLE_TERM=xterm
OSTYPE=linux-gnu
PATH=/shared/lsf/10.1/linux2.6-glibc2.3-x86_64/etc:/shared/lsf/10.1/linux2.6-glibc2.3-x86_64/bin:/shared/pm/10.1/bin:/shared/pm/10.1/linux2.6-glibc2.3-x86_64/bin:/opt/oracle/product/19.0.0/client_1/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:.:/bin:/nnhome/scesasdemo/.local/bin:/nnhome/scesasdemo/bin
PIPESTATUS=([0]="0")
POSIXLY_CORRECT=y
PPID=18637
PS4='+ '
PWD=/shared/sas/config/Lev2/SASApp
RCPRC=0
RMSQUERY=rmsquery
RUNMODE=BATCH
SASAPPSERVER=SASApp
SASCFGPATH='/shared/sas/config/Lev2/SASApp/sasv9.cfg, /shared/sas/config/Lev2/SASApp/sasv9_usermods.cfg'
SASCLIENTPORT=
SASDAEMONHOST=
SASDAEMONPORT=
SASEXEFILE=/shared/sas/apps/SASHome/SASFoundation/9.4/sas
SASGRIDBATCHPGM=''\''test.sas'\'''
SASGRIDCMDPATH=/shared/sas/config/Lev2/SASApp/GridServer
SASGRIDLOGDIR=/shared/sas/config/Lev2/SASApp/GridServer/Logs
SASGRIDSHAREDIR=/gridwork
SASGRIDWORKDIR=/gridwork/work/scesasdemo/SASGSUB-2020-12-28_08.28.34.156_test
SASREDIRCMDOPTS=-addshell
SASROOT=/shared/sas/apps/SASHome/SASFoundation/9.4
SASVJR_HOME=/shared/sas/apps/SASHome/SASVersionedJarRepository
SASVJR_REPOSITORYPATH=/shared/sas/apps/SASHome/SASVersionedJarRepository/eclipse
SASWANTJOBINFO=TRUE
SAS_COMMAND=/shared/sas/apps/SASHome/SASFoundation/9.4/sas
SAS_HOME=/shared/sas/apps/SASHome
SAS_JOB_AUTH=LiklKy8uJTAnLC4iLSIpJQ==
SBD_KRB5CCNAME_VAL=
SELINUX_LEVEL_REQUESTED=
SELINUX_ROLE_REQUESTED=
SELINUX_USE_CURRENT_RANGE=
SERVER_PID_FILE_NAME=server.scevalgrid3.pid
SHELL=/bin/bash
SHELLOPTS=braceexpand:hashall:interactive-comments:posix:privileged
SHLVL=4
SHOSTNAME=scevalgrid3
SSH_CLIENT='172.27.27.45 60575 22'
SSH_CONNECTION='172.27.27.45 60575 10.78.163.27 22'
SSH_TTY=/dev/pts/3
STRIPPATH=/shared/lsf/10.1/linux2.6-glibc2.3-x86_64/bin:/shared/pm/10.1/bin:/shared/pm/10.1/linux2.6-glibc2.3-x86_64/bin:/opt/oracle/product/19.0.0/client_1/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:.:/bin:/nnhome/scesasdemo/.local/bin:/nnhome/scesasdemo/bin:
TERM=dumb
TKPATH=/shared/sas/apps/SASHome/SASFoundation/9.4/core/sasext:/shared/sas/apps/SASHome/Secure/sasexe
TK_Default_Options=
TK_PATHLIST=/shared/sas/apps/SASHome/SASFoundation/9.4/core/sasext:/shared/sas/apps/SASHome/Secure/sasexe:/shared/sas/apps/SASHome/SASFoundation/9.4/sasexe:/shared/sas/apps/SASHome/SASFoundation/9.4/utilities/bin
TMOUT=14400
UID=634867
USER=scesasdemo
UTILITIES=/shared/sas/apps/SASHome/SASDeploymentManager/9.4/products/cfgwizard__94512__prt__xx__sp0__1/Utilities
XDG_DATA_DIRS=/nnhome/scesasdemo/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share
XDG_RUNTIME_DIR=/run/user/634867
XDG_SESSION_ID=4207
XLSF_UIDDIR=/shared/lsf/10.1/linux2.6-glibc2.3-x86_64/lib/uid
_='SASGRID: envVars ***=== START ===***'
_CUR_PATH_ENV=/shared/lsf/10.1/linux2.6-glibc2.3-x86_64/bin:/shared/lsf/10.1/linux2.6-glibc2.3-x86_64/etc:/shared/pm/10.1/bin:/shared/pm/10.1/linux2.6-glibc2.3-x86_64/bin:/opt/oracle/product/19.0.0/client_1/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:.:/bin:/nnhome/scesasdemo/.local/bin:/nnhome/scesasdemo/bin:
__LSF_JOB_TMPDIR__=/tmp/2097.tmpdir
_libcver=17
_lsf_conf=/shared/lsf/conf/lsf.conf
_lsf_enable_ego=N
_machine=x86_64
_slurm_signature_file=/var/lsf/lsfslurm
debugfile=/shared/sas/config/Lev2/SASApp/GridServer/Logs/SASGrid.scesasdemo.scevalgrid3.corp.novocorp.net.18641.20201228112949.log
field1=Linux
glibc=/lib64/libc.so.6
parm='SASBATCHWRKDIR:'\''/gridwork/work/scesasdemo/SASGSUB-2020-12-28_08.28.34.156_test'\'''
parmname=SASBATCHWRKDIR
parmval=''\''/gridwork/work/scesasdemo/SASGSUB-2020-12-28_08.28.34.156_test'\'''
role=unknown
sasgsub=/shared/sas/config/Lev2/Applications/SASGridManagerClientUtility/9.4/sasgsub
subver=3.10
tempName=scesasdemo.scevalgrid3.corp.novocorp.net.18641.20201228112949
tmp=gawk
uname_val='Linux scevalgrid3.corp.novocorp.net 3.10.0-1062.el7.x86_64 #1 SMP Thu Jul 18 20:25:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux'
version=3
SASGRID: envVars ***=== END ===***
SASGRID: Running Batch
SASGRID: SASGRIDWORKDIR=/gridwork/work/scesasdemo/SASGSUB-2020-12-28_08.28.34.156_test
SASGRID: SAS Batch Command= /shared/sas/apps/SASHome/SASFoundation/9.4/sas -logconfigloc "/shared/sas/config/Lev2/SASApp/GridServer/logconfig.batch.xml" -noterminal -sasuser work -sysin "/gridwork/work/scesasdemo/SASGSUB-2020-12-28_08.28.34.156_test/test.sas" -LOG "/gridwork/work/scesasdemo/SASGSUB-2020-12-28_08.28.34.156_test/test.log" -PRINT "/gridwork/work/scesasdemo/SASGSUB-2020-12-28_08.28.34.156_test/test.lst" -set GRIDWORK "/gridwork/work/scesasdemo/SASGSUB-2020-12-28_08.28.34.156_test"
ERROR: (SASXKINI): PHASE 3 KERNEL INITIALIZATION FAILED.
ERROR: Unable to initialize the SAS kernel.

SASGRID: SAS Batch RC=112
SASGRID: RC=112

Thanks,

Madhan M.

Re: SAS Jobs Submitted to a Queue directly goes to Exit state

AnandVyas — Tue, 29 Dec 2020 06:39:53 GMT

Hi @Madhan_cog1

How are you submitting the program? Can you share the command? Example below:

SASGSUB -GRIDSUBMITPGM /mysasfilesystem/test.sas -JOBOPTS queue=big

Re: SAS Jobs Submitted to a Queue directly goes to Exit state

Madhan_cog1 — Tue, 29 Dec 2020 06:43:07 GMT

Hi Anand,

We are submitting the program using the below command.

$sasgsub -gridsubmitpgm test.sas -JOBOPTS queue=big

Thanks,

Madhan M

Re: SAS Jobs Submitted to a Queue directly goes to Exit state

AnandVyas — Tue, 29 Dec 2020 07:10:02 GMT

Ok thanks for sharing. I hope the test.sas file is located on the same path/directory from where you are submitting the sasgsub command. If not, please use full path to the file location.

As the error in the log clearly states that there is some issue while launching SAS and it doesn't state any specific error causing this, you will have to check few things:

- Check if you are able to submit a SAS job on the node directly. You can run the below command

/shared/sas/apps/SASHome/SASFoundation/9.4/sas -logconfigloc "/shared/sas/config/Lev2/SASApp/GridServer/logconfig.batch.xml" -sysin "<replace-full-path-here>/test.sas"

- Check if the user has proper permissions to the file system of the .sas file location, work location, home directory, /tmp

- Check if you are able to submit jobs via any client instead of running it from batch mode

Re: SAS Jobs Submitted to a Queue directly goes to Exit state

gwootton — Mon, 04 Jan 2021 14:27:59 GMT

An exit code of 112 typically means the execution user does not have permission to write to the WORK location. Are you able to start SAS as scesasdemo on host scevalgrid3 by running /shared/sas/apps/SASHome/SASFoundation/9.4/sas -nodms in the terminal?