Good afternoon.
I need the help of you experts.
I have built a Job in Data Integration which I want to deploy as an SP, said SP then I must deploy it as a Web Services to consume it within SAS RTDM.
The steps I am applying are the following:
Job DI:
User Written Code:
DATA WORK.DATOS;
attrib to Length=$150;
attrib from Length=$150;
attrib asunto Length=$150;
attrib mensaje Length=$500;
to="&vto";
from="&vfrom";
asunto="&vasunto";
mensaje="&vmensaje";
RUN;
Data &_INPUT1;
attrib to Length=$150;
attrib from Length=$150;
attrib asunto Length=$150;
attrib mensaje Length=$500;
set work.DATOS;
run;
OPTIONS EMAILHOST='none.sas.com'
emailport=25;
Filename Mailbox
Email to="&vto" from="&vfrom"
Subject="&vasunto"
;
DATA _NULL_;
file Mailbox;
put "&vmensaje";
RUN;
%let vstatus=&syserr;
DATA RESPUESTA;
attrib to Length=$150;
attrib from Length=$150;
attrib asunto Length=$150;
attrib mensaje Length=$500;
attrib status length=8;
to="&vto";
from="&vfrom";
asunto="&vasunto";
mensaje="&vmensaje";
status=&vstatus;
RUN;
Data &_OUTPUT1;
attrib to Length=$150;
attrib from Length=$150;
attrib asunto Length=$150;
attrib mensaje Length=$500;
attrib status length=8;
set work.RESPUESTA;
run;
SP deployment
Deploya as Web Services
ERROR IN CI
com.sas.analytics.ph.RTDMException: <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><soapenv:Fault><faultcode
>soapenv:Server</faultcode><faultstring xml:lang="en">A 'Server Execution' type of exception occurred during execution of 'EnviarEmail' service. The exception follows: SAS completed with n
onzero SYSCC '1,012'. SYSMSG: ''.</faultstring>
I need your support to solve this problem.
Thank you.
The SYSCC variable is set when there is a warning or an error. It seems something went wrong with your mail step (probably the server none.sas.com does not exist). You are using the following data step to catch the error, so I assume that you can reset the SYSCC automatic variable after that.
But take a look at the log first, and see if that is really the case.
If you are handling errors elsewhere, you can simply put
%let syscc=0;
at the end of the program. But you may want to check it after each step, if this is production code.
Are you ready for the spotlight? We're accepting content ideas for SAS Innovate 2025 to be held May 6-9 in Orlando, FL. The call is open until September 25. Read more here about why you should contribute and what is in it for you!
Learn the difference between classical and Bayesian statistical approaches and see a few PROC examples to perform Bayesian analysis in this video.
Find more tutorials on the SAS Users YouTube channel.