topic WorkSpace server log for SASGSUB job in Administration and Deployment

WorkSpace server log for SASGSUB job

ankur_patel_aig — Mon, 10 Sep 2018 16:42:00 GMT

Hello ,

I have workspace server log enable to capture our SAS session. This is SAS GRID installation. SAS 9.4 M3

So when our user submit SAS EG session logs are generated fine. We also have users using SASGSUB to submit the job in batchmode.

But seems like SASGSUB job does not generate workspace server log.

I was under an impression that it should. Because eventually it starts workspace session. Anything that start workspace session should create this log.

Is there something I am missing ?

Re: WorkSpace server log for SASGSUB job

alexal — Tue, 11 Sep 2018 17:57:47 GMT

@ankur_patel_aig,

You have to specify logconfig.xml location using -LOGCONFIGLOC

http://support.sas.com/documentation/cdl/en/gridref/67371/HTML/default/viewer.htm#p05eo0im8mix5qn1bz77trdvzd2s.htm

Re: WorkSpace server log for SASGSUB job

johedr — Tue, 11 Sep 2018 19:36:44 GMT

@ankur_patel_aig,

SASGSUB does not start workspace servers. It runs SAS in batch mode. SASGSUB produces standard SAS logs which can be retrieved by using the GRIDGETRESULTS command.

SASGSUB uses the sasgrid script which is configured to use LOGCONFIGLOC pointing to the logconfig.batch.xml. The only other LOGCONFIGLOC specification that can be used without breaking STDIO redirection is logconfig.batch.trace.xml which puts out a lot more debugging information. Manually specifying other logconfig.xml files to produce other debugging, may break STDIO redirection, etc.