Date:         Sun, 11 Jul 2010 10:18:31 -0400
Reply-To:     Michael Raithel <michaelraithel@WESTAT.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Michael Raithel <michaelraithel@WESTAT.COM>
Subject:      Re: Gate is busy-ERROR
In-Reply-To:  <201007100552.o69KvWSC027706@malibu.cc.uga.edu>
Content-Type: text/plain; charset="us-ascii"

Dear SAS-L-ers,

Jesper responded to Art's helpful suggestion with this update to this interesting problem:

> Hi Arthur,
>
> The problem you refer occurs when signoff is omitted. My problem is
> different.
>
> However I found out - and this is important - that the code actually
> works
> when used from a Windows-client against a Windows-server but fails when
> used
> from a z/OS-client against a Windows-server.
>
> I will report this problem to SAS Institute.
>
Jesper, I have been following your issue with interest, and waiting for the right opportunity to give it a whirl on my little corner of the 'L.  I ran the following from SAS 9.2 TS2M3 on Windows XP SP 3, RSUBMIT-ing to SAS 9.2 TS2M3 on Red Hat Linux Enterprise Edition 4.0 without any errors at all:

libname pclib "C:\Program Files\SAS92\SASFoundation\9.2\core\sashelp";

options msglevel=I;
options comamid=TCP remote=MIKESMACHINE;
signon "C:\Program Files\SAS92\SASFoundation\9.2\connect\saslink\tcpunix.scr";

rsubmit inheritlib=(pclib);

proc summary nway data=pclib.shoes(where=(region="Canada"));
        class region product subsidiary;
        var   sales  returns;
output out=sumshoes sum=;
run;

endrsubmit;

signoff;


signon "C:\Program Files\SAS92\SASFoundation\9.2\connect\saslink\tcpunix.scr";

rsubmit inheritlib=(pclib);

proc summary nway data=pclib.shoes(where=(region="Canada"));
        class region product subsidiary;
        var   sales  returns;
output out=sumshoes sum=;
run;

endrsubmit;

I see that my SAS/CONNECT code is a bit different than yours... but, hey, mine worked:-)  And, it successfully does the signon, rsubmit with inheritlib, signoff and then the whole enchilada again without tears or tangles.  So, you might want to cut-n-paste the code above and see if it might work for you.  If so, you can decompose it back to something closer to what you originally had... or run as is at no extra cost to yourself!

Jesper, best of luck in all your SAS endeavors!


I hope that this suggestion proves helpful now, and in the future!

Of course, all of these opinions and insights are my own, and do not reflect those of my organization or my associates. All SAS code and/or methodologies specified in this posting are for illustrative purposes only and no warranty is stated or implied as to their accuracy or applicability. People deciding to use information in this posting do so at their own risk.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Michael A. Raithel
"The man who wrote the book on performance"
E-mail: MichaelRaithel@westat.com

Author: Tuning SAS Applications in the MVS Environment

Author: Tuning SAS Applications in the OS/390 and z/OS Environments, Second Edition
http://www.sas.com/apps/pubscat/bookdetails.jsp?catid=1&pc=58172


Author: The Complete Guide to SAS Indexes
http://www.sas.com/apps/pubscat/bookdetails.jsp?catid=1&pc=60409

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Run like hell and get the agony over with. - Clarence DeMar
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++