topic Re: Scheduling issue through smc in SAS Data Management

Scheduling issue through smc

Hema_12 — Mon, 16 Sep 2019 13:50:58 GMT

Hi,

I deployed some jobs through SAS DI and i am able to run successfully in SAS DI and i have created flow in SAS SMC and tried to schedule using SAS LSF. I am successfully schedule the job but after executing getting the following error.

NOTE: Libref STPSAMP successfully assigned from logical server.
ERROR: Libref IOTHER failed to assign from logical server.
ERROR: Teradata connection: MTDP: EM_GSSINITFAIL(235): call to gss_init failed. .
ERROR: Libref SASMDMGR failed to assign from logical server.
ERROR: Teradata connection: MTDP: EM_GSSINITFAIL(235): call to gss_init failed. .
ERROR: Libref ISMECORP failed to assign from logical server.

I am unable to getting this gss_init.

Please help me how to resolve it.

Thanks in advance.

Re: Scheduling issue through smc

AnandVyas — Tue, 17 Sep 2019 03:48:37 GMT

Hi @Hema_12 ,

Can you check if the solution provided in this KB works for you?

Thanks!

Re: Scheduling issue through smc

ErikLund_Jensen — Tue, 17 Sep 2019 16:49:36 GMT

@Hema_12

If it works in DI Studio and not in a scheduled job, the problem might be that the LIBPATH variable is set on the wrong level, i.e. in the WorkspaceServer CFG instead of the common level above, so it works in the WorkspaceServer, but is not inherited to the BatchServer.

Re: Scheduling issue through smc

SASKiwi — Tue, 17 Sep 2019 20:57:58 GMT

@Hema_12 - Another possibility is if you are defining these libnames in SMC and stored in SAS metadata they need to be pre-assigned to work in SAS batch jobs.

Re: Scheduling issue through smc

Patrick — Wed, 25 Sep 2019 08:13:27 GMT

@SASKiwi wrote:

@Hema_12 - Another possibility is if you are defining these libnames in SMC and stored in SAS metadata they need to be pre-assigned to work in SAS batch jobs.

This is likely not the issue because if using SAS DI then the code generated will include an explicit libname statement for any library used but not pre-assigned.

It would only become an issue if a metadata library definition gets change to not pre-assigned after job deployment (scheduling).