Possible uses

The pre-parse exit can be used to control what the user is allowed to specify on the CONSOLE command and in response to CONSOLE command prompts. It can also allow installation-specific keywords on the CONSOLE command. If installation-specific keywords are allowed, they should be removed before the exit returns control to the CONSOLE command.

The activation exit can be used to:

Establish a communication area for the other exits related to it.
Supply console attributes for a user
Change the initial settings that were specified by the user for the console session.
Enforce the use of console names.
Grant or deny the user CONSOLE command authority for the duration of the console session.
Note: If you do not use RACF® or the logon pre-prompt exit (IKJEFLD or IKJEFLD1) to control access to the CONSOLE command,use both the CONSOLE activation exit and the CONSPROF initialization exit to grant users CONSOLE command authority. The CONSPROF initialization exit can grant or deny CONSOLE command authority for the duration of the CONSPROF command.

The deactivation exit can be used to clean up after other exits and release the migration ID.

The 80% and 100% message capacity exits can be used to control the size of the message tables for the user. When the user's solicited or unsolicited message table becomes full, these exits can take the following actions so that messages are not lost:

Make the message table larger if the maximum table size specified in the IKJTSOxx member of SYS1.PARMLIB is greater than the current maximum table size.
Indicate that the user should have messages displayed at the terminal. This should begin to reduce the number of messages in the message table. After the table decreases to the resume percentage level specified in the parameter list, the processing of messages resumes as normal.
Indicate that the console session should be terminated.
Change the dispatching priorities of the tasks so that messages are retrieved faster.