cas table action

[elisehoo1]

something weird that i need you guys help pls 

1. program in loop to delete data from a cas table 

2. if the loop less than 10 , the program was able to executed nicely 

3. if more , the looping goes by day in few month , then the misbehavior happens , it seems locking happened to the cas table . 

4. do the syserrortext it shown this 

5. it is not a parallel run process , it is looping, one by one it hitting the table to delete some records.

6. noticed similar happened when another program keep append 1 record to the cas table. 

7. record size is small , less than 100 record , 

SYSERRORTEXT=The request to start or connect to a session failed. Specify a UUID to connect to an existing session or specify a
session name, port and host name to start a session.

The request cannot be submitted to session....The session is

[alexal]

Have you had a chance to check the CAS server logs?

[elisehoo1]

sorry , where does the log locate ? 

[alexal]

On the CAS server in /opt/sas/viya/config/var/log/cas/default/ directory.

[elisehoo1]

the error i observed from studio and the 

/opt/sas/viya/config/var/log/cas/default/ directory --"caslaunch_default_controller_daemon.e

is there any option i need to add into the code to prevent such issues ? 

thanks

[elisehoo1]

/opt/sas/viya/config/var/log/cas/default/ directory --"caslaunch_default_controller_daemon.e

[alexal]

What version of SAS Viya are you currently using? 3.4 or 3.5?

[elisehoo1]

its 3.5 ,tq

[alexal]

This is SAS Studio on SAS Viya or SAS 9?

[BrunoMueller]

Your log shows this: "The session is busy running actions that where submitted with the ASYNC= option.".

Is there a particular reason for you to use the ASYNC= option?

[elisehoo1]

nope, just i dont how to turn it off , i guess it is some default setting ?
my code pretty simple , never mention about this part.
may i know how to turn off this option ?

thanks.

[BrunoMueller]

ASYNC= is typically used for parallel action execution. It is not something that is set by default. I guess it is best to share the code with the loop and the actions called within the loop.

[elisehoo1]

here the code :

i wrote the common macro , and the macro was called in the loop . 

further questions:

1. what is conditional that cas table will be flushed from  memory ? i did one step to  save the sashdat . 

2. but i notice if i didnt load back the cas table from sashdat in momory , and execute my code the data will be replaced with the new data instead from recovery . any precaution step i can do ? 

thank @BrunoMueller 

[elisehoo1]

further questions

3.and i tried to add cas session into the auto exec but it does not seem working , is there particular reason why it does not work in autoexec file ? 

[BrunoMueller]

Add the code as image is not very helpful, it is better to either use the "insert code" or "insert SAS code" from the toolbar when adding code.

We also see only parts of the code and not the complete code. Adding the complete log will help as well.

A description of what you want to achieve helps as well in understanding.

You are using the UUIDMAC= option on the CAS statement, any particular reason for this?

[sridatae]

I have the similiar issue. here is my code.

cas mySession1 sessopts=(caslib=casuser timeout=1800 locale="en_US");

/*Assign all caslibs*/
caslib _ALL_ assign;

PROC FEDSQL sessref=mySession1 label;
SELECT COUNT (col1)
      FROM table;
quit;