1 Running an SAS program in 9S region

We had a problem in running a SAS program in 9S region.

If anyone has executed a SAS program in 9S with connection to Teradata it will be helpful.

The description of the problem is as follows:

1. We have a sample SAS program which is running fine in 1D.
2. But when we tried replicating the same program in 9S it’s not able to connect to Teradata.
3. We have imported CONNECT and other macros to 9S region. We even changed the CONNECT macro to point to the load id location in 9S.
4. We have also changed the SASAUTO location in the JCL to point to the corresponding location in 9S
5. The error displayed is: “Teradata Connection Error”
6. Apart from Connect to Teradata I have given PROC PRINT statement which is working fine in 9S. Only problem is while connecting to Teradata I am getting the error.

We got a solution for the above problem, It goes like this, Just sharing with everybody on the same.

 

In order to connect to Teradata from the 9S, your job must run specifically on the 9S04.  Even if you log on to the 9S04, your job might run on another partition (eg. 9S01, 9S02, etc) unless you add the following after your jobcard:

//*+JBS BIND SYS9S04.PERM

This will “bind” your job to the 9S04.

For example, here is the JCL I use:

//T48983J JOB 00412,'SAS TEST',MSGLEVEL=(1,1),

//  CLASS=0,MSGCLASS=V,NOTIFY=T48983

//*+JBS BIND SYS9S04.PERM

//SAS EXEC SASMSTR,LOAD='SYS3A.TERADATA.APPLOAD',

//         SASAUTO=SAS.MACLIB'

//SYSIN DD *