Using Pooled Signons Terminal

Top  Previous  Next

Pooled Signons with Terminal:

EMUE allows sign on information, including which signons are currently in use, to be stored in a database.  Each time a script is about to connect to the mainframe, EMUE retrieves the first unused signon from the database and then marks that it is in use.  This setup ensures an efficient use of signons and removes the work involved in managing signon usage.  When EMUE disconnects from the mainframe or closes, the signon is marked as not being in use anymore in the database.  EMUE supports Microsoft Access and SQL Server databases for tracking signon information.

 

Access does not fully support atomic transactions, and can therefore sometimes produce inconsistent results.   You can mitigate this issue by using the Shared=Exclusive Lock in the connection string.  Unfortunately, this also increases contention when several scripts are started simultaneously, and from our testing does not resolve all issues.   For this reason, we strongly recommend using SQL Server or SQL Server Express, which is available for free from Microsoft.

 

If no signon is available, EMUE will wait for the amount of time specified by RetryLoginDelay before retrying.  For example, if RetryLoginDelay is set to 10 and RetryLoginCount is set to 8, then EMUE will wait for ten minutes and then retry the connection and sign in.  EMUE will repeat this process until it is able to log in successfully, or until it has made 8 attempts.

 

The table where the signon information is stored is defined by SignOnInfoDBTableName and additional logging information can optionally be stored in a table defined by SignonInfoDBLogTableName.  The connection string that is used to connect to the signon database is configured by SignOnInfoDBConnectionString.

 

Additionally, in sites where pooled LU's or Terminal ID's are not available, a Terminal ID may be included with the signon and password in the database, which will effectively pool the terminal id's with the signons.  Alternatively, if there is a need to only pool terminal IDs (and not sign ons), that can be configured with a few SetStartup settings as well.

 

SetStartup DeviceName "UsePool"

 

The remainder of the pooled signon settings (SignOnDBConnectionString, SignOnDBTableName, and SignOnDBLogTableName) are the same as they would be for pooling signons.

 

The Access databases and a SQL Server database script are available for download at www.databoundhealthcare.com under Support Downloads in the Downloads menu.

 

Once the database set up, simply add each signon and corresponding password to the SignOnInfoDBTableName table.

 

In order for EMUE to use pooled signons from the database, the SignOn field must be left blank, and the SignonInfoDBConnectionString and SignOnInfoDBTableName must be supplied.

 

Sample Connection Strings:

 

SQL Server:  Provider=SQLNCLI;Server=ServerName;Database=DatabaseName;SignOnInfo;Trusted_Connection=yes;

 

Access 2007: Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\EMUE\SignOnInfo.accdb;Persist Security Info=False;Mode=Share Exclusive;

 

Access 2003: Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\EMUE\SignOnInfo.mdb;User Id=admin;Password=;Mode=Share Exclusive;

 

Sample 1:

The following statement uses the SetStartup command SignOnINfoDBConnectionString to store the signon information for a SQL database.

SetStartup SignOn ""

SetStartup Password ""

SetStartup SignOnInfoDBConnectionString "Provider=SQLNCLI;Server=SQLSERVER01;Database=db01;Trusted_Connection=yes;"

SetStartup SignOnInfoDBTableName "SignOnInfo"

SetStartup SignOnInfoDBLogTableName "LogInfo"

 

Sample 2:

The following statement uses the SetStartup command SignOnINfoDBConnectionString to store the signon information for a Access 2007 database.

SetStartup SignOn ""

SetStartup Password ""

SetStartup SignOnInfoDBConnectionString "Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\emue\Test\SignonDB\SignOnInfo.accdb;Persist Security Info=False;"

SetStartup SignOnInfoDBTableName "SignOnInfo"

SetStartup SignOnInfoDBLogTableName "LogInfo"

 

Sample 3:

The following statement uses the SetStartup command SignOnINfoDBConnectionString to store the signon information for a Access 2003 database.

SetStartup SignOn ""

SetStartup Password ""

SetStartup SignOnInfoDBConnectionString "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\emue\Test\SignonDB\SignOnInfo.mdb;UserID=admin;Password=abc123;Mode=Share Exclusive"

SetStartup SignOnInfoDBTableName "SignOnInfo"

SetStartup SignOnInfoDBLogTableName "LogInfo"