'sas' is not recognized as an internal or external command

[KVRamana]

Hi,

I'm Trying to execute SAS program using JCL in Micro Focus environment triggered MFSAS-FDS utility provided by Micro Focus. When I submitted the Job(JCL) getting below error not able to proceed further:

C:\SAS\SASWORK>sas JCL401074STEP10.SAS -sysparm "JOBID=JCL4;dbuser=JESUSER;database=DB2T;options='';"

'sas' is not recognized as an internal or external command, operable program or batch file.
RETURN-CODE=9009

*********** Warning *****************
PGM=SASPIPE OPEN ERROR
SAS Log file not found
SASLOGF-STATUS: 35
*********** Warning *****************

Thank you,

Ramana.

[Kurt_Bremser]

Most likely your SASHome\SASFoundation\9.4 directory is not in your PATH environment variable. Always use absolute paths to call external programs.

[KVRamana]

Hi Kurt,

Thank you very much for the quick clue on the error. Can I know if some sample temple for the Environment Variables to be declared in Micro Focus enterprise server to connect to SAS Server. I know Both Servers are in the same domain.

Thank you in advance,

Ramana.

[Kurt_Bremser]

The fact that the JCL tries to start SAS from this path

C:\SAS\SASWORK>

lets me suspect it already does this on the SAS server.

You then need to get JCL to use the full path to the SAS executable, which usually is

C:\Program Files\SASHome\SASFoundation\9.4\sas.exe

For the details, you need to get your SAS server admin and the MicroFocus admins to work together.

Disclaimer: our MicroFocus mainframe environment runs on Linux, and the scheduler (and therefore the JCL scripting) is still done on a regular z/OS instance.

And SAS jobs are run from the scheduler via SSH/SFTP.

[KVRamana]

Thank you very much Kurt!

-Ramana.

[KVRamana · Accepted solution]

Hi Kurt!  Yes, you are right, it has things beyond the developer's control. Micro Focus (MF) has a SAS-FDS utility to make SAS work through JCL if both SAS and Micro Focus are on the same box. In our case, both are on different servers (both are Windows servers - No Unix or Linux), and I have worked extensively with the MF team to tailor the SAS-FDS Utility to have remote connectivity to the SAS server as and when a JCL step encounter SAS program. Things are up and running now.

Thank you for the clue which showed me a way to get an extraordinary achievement.  

"It's amazing to see what we can achieve, no matter who gets the credit".

Have a nice time!!!

-Ramana.