Problems with logging in to newly configured Sunquest servers and/or servers with new security features


Increasingly, OL Monitor users have been running into problems with the macro logging in to newly configured Sunquest servers and/or servers with new security features.  SSL, SSO, and some Linux servers present additional hurdles at login that the macro is not programmed to handle.  For most cases, particularly SSL, the Custom Prompt/Reply feature has been adequate to get past additional prompts.  However, some servers present more than one additional prompt to deal with.  For example, an additional Username prompt appears and then a Password prompt:



Presently, OL Monitor is only equipped to handle one of these new prompts using the Custom Prompt feature.

Therefore, a user would have to intervene on the SmarTerm macro and type in the USERNAME or PASSWORD to get the macro to the FUNCTION prompt.

However, there is nothing stopping you from recording your own login macro to fix this problem.  Here are instructions on recording the login macro and then adding a line of code to call the OL Monitor macro:

Step 1:  Close OL Monitor and SmarTerm.  Launch SmarTerm and create a new (SSL or Telnet) session.  Configure to connect to your Sunquest server.

Step 2:  SmarTerm should ask if you want to record a login macro; click yes.

Step 3:  Login to Sunquest.  The login macro should stop recording automatically when you reach the FUNCTION prompt.  Otherwise, click stop.

Step 4:  Save the new session and close SmarTerm.  Re-launch SmarTerm and load the new session you just created.  Ensure that the new session logs you into the new system.

Step 5:  Now we will modify the login macro to call the OL Monitor macro.  Press the green button to view macro options.  From the drop-down list at bottom, choose “Pre-Defined session macros”.              In the macro list that appears, choose “login macro”.

Step 6:  Press the edit button to edit the macro.  You will see the macro code.  It is not important to understand this code.  We just need to find the end of the macro code.

Scroll down till you find the line that says End Sub

Place the cursor directly above that line and type Call Ol_Mon.

Click Save and exit the editor.

Step 7:  Close SmarTerm and re-launch the new session to test again. 

You should see the login macro complete, and then the OL Monitor macro take over and begin stepping through the OL log menus.

Step 8:  At this point, if the OL macro has taken over control successfully we are ready to deploy the new session to the OL Monitor folder. 

Click the green triangle button and stop the macro.

Click File- Save As. 

Browse to the OL Monitor folder in Public Documents.  The path is:


Select the existing OL_Monitor.stw session file and click save.

Yes overwrite existing file.

Step 9:  Now close SmarTerm and launch OL Monitor.

Leave a Reply

Your email address will not be published. Required fields are marked *