Date:         Thu, 11 Apr 2002 20:16:42 -0700
Reply-To:     Wing <wstsui@IRD.GOV.HK>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Wing <wstsui@IRD.GOV.HK>
Organization: http://groups.google.com/
Subject:      Re: (MAR) RE: Can I update a SAS dataset using SAS Script?
Content-Type: text/plain; charset=ISO-8859-1

Thank you all so much on your input.
The problem is that how can I distinguish the connection failure by
its return code as I only need to update the dataset if, and only if,
the connection is failed because of an expired userid/password.
I am thinking of getting use of the SAS log.  Any other suggestion /
idea?

Thanks so much!

Wing.
RAITHEM@WESTAT.COM (Michael Raithel) wrote in message news:<08B08C9FA5EBD311A2CC009027D5BF8103A87B40@remailnt2-re01.westat.com>...
> Dear SAS-L-ers,
>
> Wing posted the following question:
>
>
> >Dear All,
> >
> >Please Help!
> >How can I update a SAS dataset depending on the return message from a
> >remote UNIX signon?
> >My situtation:
> >1.  From AF frame, using SCL to capture username and password
> >2.  Execute a TCPUNIX Script for remote unix signon.
> >3.  From script, if the username / password expired (unix signon return an
> >error code of 3004-302, update a shared dataset (on the unix system) then
> >abort.
> >
> >How can I achieve that?
> >Please help.
> >
>
> Wing, I hate to be so negative right from the start, but I don't believe
> that #3, above, is possible to do.  My reasoning is that you will never
> really have logged onto the Unix server if you have an expired username /
> password and your Unix signon fails.  So, you are powerless to do anything
> on the Unix server--such as updating a shared data set--since you are not
> ever logged on.
>
> I think that you are going to have to do something along the following:
>
> 1. If you are unsuccessful in your Unix logon attempt (#3, above) have your
> AF application write the username and password to a PC file.  Hopefully, you
> can have this file written to a specific directory on a shared network
> drive.
>
> 2. Use the AT NT "job scheduler" to kick off a script that FTP's the "I
> couldn't log onto Unix" files to a specific directory on Unix.  This script
> could be scheduled for execution at intervals that you deemed reasonable.
>
> OR:
>
> 3. Use the AT NT "job scheduler" to kick off a SAS program that processes
> the "I couldn't log onto Unix" files, reading them, connecting to the Unix
> server, and updating the "shared dataset (on the unix system)".  This script
> could be scheduled for execution at intervals that you deemed reasonable.
>
> The above steps, while technically vague, might be a good blueprint for
> resolving your problem.
>
> Wing, best of luck to you in your effort to resolve expired Unix logon IDs
> in your SAS/AF programs!
>
>
> 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
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Careful with that axe, Eugene. -- Pink Floyd
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++