LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (December 2001, week 3)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Thu, 20 Dec 2001 18:18:25 +0100
Reply-To:     Peter Crawford <peter.crawford@DB.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Peter Crawford <peter.crawford@DB.COM>
Subject:      sas/connect script issues
Content-type: text/plain; charset=iso-8859-1

Hi it is now (v8.1) very convenient that signon scripts support macro variables and will even execute macros. So, it becomes practical to have a common script with macrovars for userid and password (especially useful for batch jobs using remote connect sessions)

Also convenient, is the occasional line like log "SIGNON: waiting for startup %now";

Where that %now macro resolves to the current time on the client.

One problem for which your help will be appreciated surfaces when I want some diagnostics. I use invocation(only) option -verbose like type 'sas -dmr -comamid tcp -device grlink -noterminal -verbose -nosyntaxcheck' LF;

Unfortunately, the standard tcpunix signon script was not handling the - verbose dialog successfully, with the normal script lines

waitfor 'SESSION ESTABLISHED', 90 seconds : nosas; log 'NOTE: SAS/CONNECT conversation established.'; stop;

The expected text was not being displayed. Instead the output from -verbose is displayed and this seems to need some interaction, before the normal dialog output continues.

On one trace-ed session, I noticed text like "Standard input" appearing just before the connect script timed-out.

For a quick fix I added some lines to my copy of the script after type 'sas -dmr -comamid tcp -device grlink -noterminal -verbose -nosyntaxcheck' LF;

I added waitfor_session: waitfor 'SESSION ESTABLISHED' , 'tandard input' : standard_input , 90 seconds : nosas;

log 'NOTE: SAS/CONNECT conversation established.'; stop; standard_input: log "SIGNON: waiting for startup %now"; type ' ' LF ; goto waitfor_session ;

So, on to the questions....................... Is there some extra options to add to that SAS start up command to direct all outputs to the connect dialog buffers ? or is there a way to ensure that "Standard input" can be relied upon ?

Have I stumbled on a reliable solution or can I expect the connect dialog to change at the next release of sas and/or aix ??!!

this issue has been tracked as ref uk1006677

seasons greetings Peter Crawford

--

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.


Back to: Top of message | Previous page | Main SAS-L page