Sebastian is absolutely correct in what he says. Here are a couple more comments. As Sebastian says, you will use EG to create SAS code, either using the built in tasks or directly using the code editor, and then that code will be submitted to a SAS environment for execution. If the code will be running on a remote server (not your local machine), it is very common for the SAS and EG setup to not permit X commands, to reduce the risk of crashing the server. If you find that your SAS code containing X commands (like your example) don't work, that may be the reason. In the example you provide, you are using an X command to start a SAS session. I can't think of any reason why you would need to do that; you are already running a SAS session that is executing the code created in EG. Tom
... View more
