Menu Bar

LOGONRCS: Use a REXX exec to control session logon, instead of a script


Automation Point is designed to use Script files to initialize and configure sessions when necessary. This application shows how to do most of the difficult work in a REXX program instead of a script, so that the sessions get initialized faster, and are more robust.

The Automation Point script language is very minimal:

  • It has the "IF-THEN" concept, but no "ELSE" concept.

  • It has no variable support, so values (like passwords) need to be hard-coded into it.

  • It has no "DO WHILE" feature.

  • All of the timeout values need to be set to the highest possible values. This causes Slow startup & shutdown of automation

Automation Point dispatches a script to run at key times, such as:

  • When session needs logged on.

  • When an automated session is lost, or when the screen becomes unrecognizable.

  • When Automation is restarted.

Each time a script is run, AP issues the following message:

AXC0213I Script file LOGONRCS.SCR active in session MVSA

You can trap this msg in a rule and schedule a REXX exec which does the actual work. The Automation Point Console driver is suspended until the script completes, so the script must be made to "wait around" until the REXX exec "allows it" to exit.

The following set of programs work to gether to implement this concept for logging onto Remote Console/MVS. The same concept could be implemented for any kind of session. There are several components:

  • LOGONRCS.RUL - A set of Automation Point rules that watch to see when the LOGONRCS.SCR script starts and ends.

  • LOGONRCS.SCR - An automation Point script file designed to coordinate with the LOGONRCS.CMD REXX exec. Note that it doesn't do any work of it's own: it just "sits and waits" until the REXX exec tells it to exit. This is so that the Automation Point console driver doesn't start typing on the session before the REXX exec is finished. This script is completely generic, so you could copy it to a different filename and use it to coordinate with other logon REXX execs.

  • LOGONRCS.CMD - The REXX exec that does the actual work of logging on. You will need to customize this script to your site - it searches for your site's VTAM logon screen, and will need to determine what VTAM applid, userid and password to use to logon to Remote Console/MVS. A table is provided for this function.



Download zipped version of the above files and any required subroutines


Note: This sample is provided "as-is", and no warranty is provided by ProTech. Use at your own risk! However, feedback on this sample is welcomed by the author! E-mail address: bstark@protechpts.com