Configuring and Writing REXX › Binding a REXX Program to a CA Automation Point Session › How Does Binding Work in CA Automation Point?

How Does Binding Work in CA Automation Point?

Using the BIND.cmd program to bind a REXX program to a session is a user-implemented coding standard. It does not bind a session in the same way that you would expect binding to work on the z/OS system.

To be effective at preventing REXX programs other than the current one from writing to a session, all of your REXX programs must implement the BIND.cmd and UNBIND.cmd programs.

If one of your REXX programs does not adhere to the standard, it can still write to a session. Also, CA Automation Point and your rules can always write to a bound session.

The BIND.cmd and UNBIND.cmd programs set and clear (respectively) a CA Automation Point status variable (&BIND_sessname). When a REXX program that adheres to the standard tries to bind a session, it checks the status variable first. If the variable is clear, the program binds the session—preventing your other REXX programs from writing to that session.