×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Tim,
There are certain "events" that occur in the system where it makes sense
for some of your own custom code to run.
For example, when someone changes their password, wouldn't it be nice if
you could run some of your own code to verify that the password matched
the companies rules? Then you could institute any password rules you
want (no matter how unusual) because YOU write your own code to verify
that the password is legal.
If you were IBM and writing the operating system this would be
relatively easy. You have the code for the operating system, so you
just stick your routine in the right place, and you're set to go. But
if you're not privy to the code where it asks the user for a password
change, what can you do?
That's the idea of an exit point. It's an "event" that occurs in the
system, such as when a user changes a password, or when telnet
initializes a new DEVD for a terminal, or when an FTP command is issued,
or when a new job is started, etc, etc. These "events" are called
"exit points" -- points in which IBM's code (or other software vendors,
for that matter) can stop and run a program that YOU supply.
An exit program is simply the program that's run during these events.
There's a tool in i5/OS called the "registration facility" that
maintains a list of exit points, and lets you assign programs to them.
type WRKREGINF to see what I mean.
Tim Gornall wrote:
There has been a lot of "talk" in one of the recent treads mentioning exit
programs. I have heard the term for years, but have never worked with them.
Can some briefly explain what they are, how they are used, maybe point me to
a common IBM supplied program I could look at, etc. Thanks, Tim
midrange.com
