topic Re: Stored Process Behavior in AMO in SAS Enterprise Guide

Stored Process Behavior in AMO

satoko — Thu, 03 Dec 2009 06:49:23 GMT

Hi

When all stored process executing in AMO, two times clientconnecition occur in Stored Process Server log.
In EG and WRS, one time clientconnection do.

The second clientconnection seems to execute stored process by Stored Process Server log.
But I can't figure out what the first clientconnection is doing.
Does anyone know what is the first clientconnection's task?

Stored Process Server Log file in executing Stored Process is as below.

=============== STP Context 22 Log End ===============
20091030:16.38.56.22: 00002676: Client connection (41) closed.
20091110:10.22.17.01: 00002677: New client connection (42) accepted from server port 8612 for user satoko. Encryption ←The first clientconnection
level is Credentials using encryption algorithm SASProprietary. Peer IP address and port are 172.26.28.238:4048.
20091110:10.24.35.68: 00002684: Client connection (42) closed.
20091110:10.24.54.43: 00002685: New client connection (43) accepted from server port 8612 for user satoko. Encryption
level is Credentials using encryption algorithm SASProprietary. Peer IP address and port are 172.26.28.238:4062. ←The second clientconnection
20091110:10.24.54.58: 00002693: 43:satoko: STP: 23: Executing /home/sasinst1/stp satoko_test1.sas
20091110:10.24.55.30: 00002693: 43:satoko: STP: 23: Execution Complete. Status=0
=============== STP Context 23 Log ===============

Thanks

Re: Stored Process Behavior in AMO

Vince_SAS — Mon, 07 Dec 2009 17:40:38 GMT

I suggest you try posting this question in the SAS Enterprise Guide Forum:

http://support.sas.com/forums/forum.jspa?forumID=10

Vince DelGobbo
SAS R&D

Re: Stored Process Behavior in AMO

reneeharper — Mon, 07 Dec 2009 20:59:20 GMT

Moved this to the Enterprise Guide forum per Vince's suggestion.

Re: Stored Process Behavior in AMO

ChrisHemedinger — Wed, 09 Dec 2009 14:11:47 GMT

From our Add-In expert here at SAS:

In the 2.1 version of the Add-In, we did make two connections: one to verify the stored process exists and gather prompt information, and the next to actually execute the stored process.

In the 4.2 version, both EG and the Add-In execute stored processes in the same way, and should use just one connection to do it.

Chris