z/OS TSO/E Customization
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Parameter descriptions for the activation exit

z/OS TSO/E Customization
SA32-0976-00

The activation exit receives the standard exit parameter list with the following exceptions:
  • The parameters are in key 1 storage.
  • The command buffer, new command buffer, and exit reason code fields are not used. Their values in the parameter list are:
    Key
    X'00'
    Length
    X'04'
    Data
    X'00'

For a description of the standard exit parameter list, see TSO/E standard exit parameter list.

Figure 1 shows the exit-dependent data that the activation exit receives beginning at offset +36 (decimal) in the parameter list.

Figure 1. Exit-dependent data for the CONSOLE activation exitExit-dependent data for the CONSOLE activation exit
Solicited Message Table Initial Size (Parameter Entry 10)
This parameter contains the initial size of the solicited message table. This exit can change the initial size if it determines that another value is more appropriate. The value specified by the exit must not be greater than the value specified in parameter 12.
Unsolicited Message Table Initial Size (Parameter Entry 11)
This parameter contains the initial size of the unsolicited message table. This exit can change the initial size if it determines that another value is more appropriate. The value specified by the exit must not be greater than the value specified in parameter 13.
Solicited Message Table Maximum Size (Parameter Entry 12)
This parameter contains the absolute maximum size of the solicited message table. This is the value specified in the active IKJTSOxx member of SYS1.PARMLIB. This parameter is for information only. Any changes to this parameter have no effect on processing.
Unsolicited Message Table Maximum Size (Parameter Entry 13)
This parameter contains the absolute maximum size of the unsolicited message table. This is the value specified in the active IKJTSOxx member of SYS1.PARMLIB. This parameter is for information only. Any changes to this parameter have no effect on processing.
Flags (Parameter Entry 14)
This parameter contains a word consisting of flags, in which the command passes indicators to the exit. The flags are described in Table 1.
Table 1. Flags passed to the CONSOLE activation exit
Flag Meaning
X'80000000' Solicited messages are to be displayed at the terminal. If this bit is off, solicited messages are not to be displayed. This value can be changed by the exit.
X'40000000' Unsolicited messages are to be displayed at the terminal. If this bit is off, unsolicited messages are not to be displayed. This value can be changed by the exit.
X'20000000' The console profile provided to the exit is a default profile. If this bit is off, a profile was obtained from either RACF® or the logon exit IKJEFLD1.
X'10000000' CONSOLE command authority bit. This bit is on if the user has CONSOLE command authority. If this bit is off and the exit determines that the user should have CONSOLE command authority, the exit should turn this bit on. If this bit is on and the exit determines that the user should not have CONSOLE command authority, the exit should turn this bit off.
X'0FFFFFFF' Reserved.
Name of Console to Activate (Parameter Entry 15)
This parameter contains the name of the console to be activated. If the exit changes the console name, the length field should also be updated to reflect the correct length of the console name.
Pointer to OPERPARM area (Parameter Entry 16)
This parameter allows the installation to return an OPERPARM area (mapped by IEZVG111) to the CONSOLE command for use during activation. See the OPERPARM parameter on the MCSOPER macro in for details on how to supply this information. The exit must issue the GETMAIN macro to obtain storage for this area and return a pointer to it in this parameter. If the exit returns a pointer, it must also set the key field to 2 (indirect data returned) and the length field to the length of the area being returned. This value is passed to the deactivation exit in parameter 11 of that exit.
Note: You are responsible for issuing the FREEMAIN macro to free this storage in the deactivation exit unless you choose a task-related subpool.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014