BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
Yarlanil59
Obsidian | Level 7

A user is having a problem with code running when submitting to the grid. He only checked that the GSUB command in putty submitted. He didn’t actually check that the code ran successfully. It turns out that it didn’t.

He submitted a job earlier today using putty and GSUB.SH command. He just tried checking the log to see if it was done, and it looks like it never submitted.

Then took a short piece of code to try to submit something simple but similar in EG. The log below is from running the code in EG.

When run this:

%let user = XXXXX;
%let password = 'XXXXX;

LIBNAME PRD_SAS NETEZZA SERVER='NETEZZASRV' DATABASE=PRD_SAS_1 USER=&USER. PASSWORD=&PASSWORD.;

EXECUTE (CREATE TEMPORARY TABLE ORGANIZATION AS
SELECT ORG_KEY,
LVL_2_NM AS MARKET,
LVL_3_NM AS AREA,
BILL_SYST_LVL_4_NM AS FRANCHISE,
OPER_UNIT_NM,
'Y' AS ORG_MATCH
FROM PRD_DL_SAS..DL_ORGANIZATION
WHERE EFF_END_DAY_KEY > &END_DATE.
AND EFF_START_DAY_KEY <= &END_DATE.
AND LVL_2_NM NOT IN ('EXEC VICE PRES CONT OPS', 'ORPHAN VALUES')
AND HIER_NM <> 'ORPHAN VALUES'
AND ORG_PART_KEY IN &ORG_NUM.
) BY CON1;

I get this in the log:

1 ;*';*";*/;quit;run;
2 OPTIONS PAGENO=MIN;
3 %LET _CLIENTTASKLABEL='Program1';
4 %LET _CLIENTPROJECTPATH='';
5 %LET _CLIENTPROJECTNAME='';
6 %LET _SASPROGRAMFILE=;
7
8 /* NOTE: ODS statement generation is turned off in options. */
9
10 OPTIONS DEV=JAVAIMG;
11 GOPTIONS XPIXELS=0 YPIXELS=0;
12
13 /* BEGIN: Results options macro variables */
14 %LET _GOPT_DEVICE = JAVAIMG;
15 %LET _GOPT_XPIXELS = 0;
16 %LET _GOPT_YPIXELS = 0;
17 %LET _GOPT_GFOOTNOTE = NOGFOOTNOTE;
18 %LET _GOPT_GTITLE = NOGTITLE;
19 %LET _ODSOPTIONS_GRAPHCODEBASE = ;
20 %LET _ODSDEST_LISTING = ;
21 %LET _ODSDEST_HTML = ;
22 %LET _ODSDEST_RTF = ;
23 %LET _ODSDEST_PDF = ;
24 %LET _ODSDEST_SRX = tagsets.sasreport12;
25 %LET _ENCODING_SRX = UTF8;
26 %LET _ODSSTYLE_SRX = Analysis;
27 %LET _ODSSTYLESHEET_SRX = (URL="file:///D:/Program%20Files/SAS/EnterpriseGuide/4.3/Styles/Analysis.css");
28 /* END: Results options macro variables */
29
30 GOPTIONS ACCESSIBLE;
31 %gridClientPrecode;
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
2 The SAS System 13:27 Wednesday, March 22, 2017

ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
76
76 ! rsubmit grid &_GridInheritLibs;
ERROR: A link must be established by executing the SIGNON command before you can communicate with GRID.
NOTE: Subsequent lines will be ignored until ENDRSUBMIT.
ERROR: Remote submit to GRID canceled.
77 %gridClientPostcode;
78
79
80 GOPTIONS NOACCESSIBLE;
81 %LET _CLIENTTASKLABEL=;
82 %LET _CLIENTPROJECTPATH=;
83 %LET _CLIENTPROJECTNAME=;
84 %LET _SASPROGRAMFILE=;
85
86 ;*';*";*/;quit;run;
87 ODS _ALL_ CLOSE;
88
89
90 QUIT; RUN;

 

Any suggestion?

1 ACCEPTED SOLUTION

Accepted Solutions
Yarlanil59
Obsidian | Level 7

Our is SAS 9.2 environment. In SAS 9.2 we need to deploy SID in Metadata from deployment Manager as well along from updating license in setup utility. 

View solution in original post

2 REPLIES 2
JuanS_OCS
Amethyst | Level 16

Hello @Yarlanil59,

 

3 approaches. For the first 2, have you read already:

http://support.sas.com/kb/48/456.html 

or 

https://communities.sas.com/t5/Base-SAS-Programming/strange-SYSLPUT-warning/td-p/127253

?

 

For the third one, I see you have GOPTIONS enabled, when probably you don't need them. You can disable this option like this:

https://communities.sas.com/t5/SAS-Enterprise-Guide/Turning-off-goptions-in-SAS-EG-code-node/td-p/13...

Yarlanil59
Obsidian | Level 7

Our is SAS 9.2 environment. In SAS 9.2 we need to deploy SID in Metadata from deployment Manager as well along from updating license in setup utility. 

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

CLI in SAS Viya

Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 2 replies
  • 1364 views
  • 0 likes
  • 2 in conversation