Find out the rest of the story about PRGDLTRCDS and Watch considerations.

By Bruce Vining

This is the sixth in a series of articles on detecting that certain messages have been sent on your system and then making processing decisions based on those messages. The underlying technology, known as Watch support, became available with V5R4.

Learn how to control the RGZPFM operation.

Written by Bruce Vining

This is the fifth in a series of articles on detecting that certain messages have been sent on your system and then making processing decisions based on those messages. The underlying technology being used is known as Watch support and became available with V5R4.

Learn about the V6R1 watch enhancement and understand a file's DLTPCT attribute.

By Bruce Vining

This is the fourth in a series of articles on detecting that certain messages have been sent on your system and then making processing decisions based on those messages. The underlying technology, known as "watch support," became available with V5R4.

Learn more ways to use exit programs for the Watch for Event exit point.

By Bruce Vining

This is the third in a series of articles on watching for certain messages on your system and then making processing decisions based on those messages. The underlying technology being used is known as "watch" support and became available with V5R4. In this article, we will look at how to automate the re-enabling of a specific *USRPRF when the *USRPRF has been disabled because of too many invalid password attempts--that is, the number of signon attempts has exceeded the QMAXSIGN system value.

Write an exit program for the Watch for Event exit point.

By Bruce Vining

This is the second in a series of articles related to watch support on the system. The previous column, "One Approach to System Automation," introduced the concept of watches and the Start Watch (STRWCH) command. Also provided in that article was the source for a watch exit program that would be called when the message CPD1689 (Local system time has been adjusted) was sent to the QHST history log. We did not, however, have time to discuss the mechanics of how the program worked. In this article, we will look at the actual program flow.