I am rather alarmed at the thought that someone might sign onto the server and use it as a client PC. The possibility for tears and apologies to other server clients seems rather high.

However, I have connected from a PC back to itself as a means of proving the SAS server or spawner (in earlier versions) has started. It may only require a suitable scripted or unscripted approach and the provision of the appropriate ip address and port.

In a sense, the SAS MP Connect approach can use this philosophy to make a machine use its processor(s) to full capacity.

You will have quite a lot of redundant code, especially with uploads and downloads, but I would think a fair amount of code migration will involve replacing the ****Load procedure calls with Copy procedure calls, and the shared environment will make the Sys*Put macro calls redundant. Library changes should be reasonably simple also.

Kind regards

David

The Moving Finger writes; and, having writ, Moves on: nor all your Piety nor Wit Shall lure it back to cancel half a Line, Nor all your Tears wash out a Word of it

Omar Khayyam (trans: Edward Fitzgerald)

-----Original Message----- From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of rob Sent: Monday, 2 April 2007 4:23 PM To: SAS-L@LISTSERV.UGA.EDU Subject: Can the same box be both Client and Server?

I am investigating the conversion / migration of our SAS environment.

We intend to move from a Client Server Model (PC to Unix) to a MS Windows Server Based environment.

We have quite a lot of client/server code using remote submits, proc download, sysrput and syslput, remote library sevices etc. Obviously we need to modify this code to run in the new environment.

My question is:

Can I define our new Windows based Server as both the client and server in SAS? This would allow the code to run with minimal changes. We could then convert to the Server-based sas code at a more leisurely pace.

Any other ideas? Comments?

Thanks

Rob.

************** IMPORTANT MESSAGE ***************************** This e-mail message is intended only for the addressee(s) and contains information which may be confidential. If you are not the intended recipient please advise the sender by return email, do not use or disclose the contents, and delete the message and any attachments from your system. Unless specifically indicated, this email does not constitute formal advice or commitment by the sender or the Commonwealth Bank of Australia (ABN 48 123 123 124) or its subsidiaries. We can be contacted through our web site: commbank.com.au. If you no longer wish to receive commercial electronic messages from us, please reply to this e-mail by typing Unsubscribe in the subject line. **************************************************************