Implementing timeout delete

DSHIPIDL={020000|hhmmss}

Specifies the minimum time, in hours, minutes, and seconds, that an inactive shipped terminal definition must remain installed in this region. When the CICS timeout delete mechanism is invoked, only those shipped definitions that have been inactive for longer than the specified time are deleted.

You can use this parameter in a transaction routing environment, on the application-owning and intermediate regions, to prevent terminal definitions having to be reshipped because they have been deleted prematurely.

hhmmss

Specify a 1 to 6 digit number in the range 0-995959. Numbers that have fewer than six digits are padded with leading zeros.

DSHIPINT={120000|0|hhmmss}

Specifies the interval between invocations of the CICS timeout delete mechanism. The timeout delete mechanism removes any shipped terminal definitions that have not been used for longer than the time specified by the DSHIPIDL parameter.

You can use this parameter in a transaction routing environment, on the application-owning and intermediate regions, to control:

• How often the timeout delete mechanism is invoked.
• The approximate time of day at which a mass delete operation is to take place, relative to CICS startup.

0

The timeout delete mechanism is not invoked. You might set this value in a terminal-owning region, or if you are not using shipped definitions.

hhmmss

Specify a 1 to 6 digit number in the range 1-995959. Numbers that have fewer than six digits are padded with leading zeros.

For details of how to specify system initialization parameters, see Specifying CICS system initialization parameters.

After CICS startup you can examine the current settings of DSHIPIDL and DSHIPINT. For flexible control over when mass delete operations take place, you can reset the interval until the next invocation of the timeout delete mechanism. (The revised interval starts from the time the command is issued, not from the time the remote delete mechanism was last invoked, nor from CICS startup.) Alternatively, you can invoke the timeout delete mechanism.