As I said earlier, you cannot see them because they are hidden. The only way to see them is to use the lsof command on the cas process. But depending on your environment, it might be tricky to run it. Here are some examples:   sessionPID=`ps -u ${userid} -o user:12,pid,ppid,stime,cmd | /usr/bin/grep cas | grep -v grep | awk '{print $2}'` masterPID=`ps -u cas -o user:12,pid,ppid,stime,cmd | grep "cas join" | awk '{print $2}'` echo echo "*** Session CAS tables: files in CAS_DISK_CACHE ***" echo lsof -a +L1 -p ${sessionPID} | grep _${sessionPID}_ echo echo "*** Global CAS tables created in this CAS session: files in CAS_DISK_CACHE ***" echo sudo -u cas lsof -a +L1 -p ${masterPID} | grep _${sessionPID}_ ... View more

Hi hrczeglo, you'll have to do something like below.  We use the status=s option to put the _status info into the s CASL variable and then we use symputx function to put the _status statusCode in the syscc macro variable.     proc cas; simple.summary result=r status=s / inputs={"actual","predict"} subset={"sumb"} table={name="prdsale" caslib="dm" groupby={"prodtype"}} casout={name="prdsaleSum" caslib="dm" replace="true" replication=0}; print _status; call symputx('syscc', s.statusCode, 'G'); quit; %put ***syscc is &syscc.***;     The above example fails because the "sumb" variable does not exist and the "print _status" and "%put ***sycc is &syscc.***; statement outputs look like this:     {severity=2,reason=6,status=Error parsing action parameters.,statusCode=2720411} NOTE: PROCEDURE CAS used (Total process time): real time 0.02 seconds cpu time 0.00 seconds 90 91 %put ***syscc is &syscc.***; ***syscc is 2720411*** ... View more