Create the ability to delete TSQs at a specific time

Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Transaction Processing
Product - CICS Transaction Server

For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Transaction Processing
Product - CICS Transaction Server

After further investigation, the conclusion has been reached that providing a specific time as well as an expiry interval is not something we will be looking at providing. We will investigate instead requests we have had to reduce the expiry interval  to less than an hour.

This is a candidate for a future release.

Reply by email from Roger:

We could run a transaction to delete the queues at 5PM but then we have
to determine the exact names of the queues to be deleted by browsing the
TSQ names with generic "keys".

The transaction would have to have a mask for the TSQ names to be
deleted supplied via most likely a sysin dataset. The sysin dataset
would have to be updated every time it was determined another queue had
to be deleted

It would be much simpler and less intrusive to create and install a TSM
definition with a mask and have CICS take care the deletion.

By "in use" I am guessing you mean "LOCKed". Most of the queues I am
concerned with get created when an application initially starts or a
user signs on to the application and are not updated after they are
created so they should not get "LOCKed". I would not expect this
facility to work if the queue is locked.

Hi Roger,
     Forgive us if we probe a little bit more into the real requirement here. Using your example, one of the developers was asking why this is not achieved by scheduling a transaction to run at 5pm that issues an EXEC CICS SET TSQUEUE() DELETE ? What do you expect to happen if the TSQUEUE is in use at 5pm ?

Thanks,
John Tilling

Independent of use I would like to be able to delete a TSQ at a specific time.

With the existing function, an EXPIRYINT of 8 hours means that the TSQueue would be deleted if it had not been used for 8 hours. It sounds like you want a facility that deletes the queue regardless ? Is this correct ?

Are you aware of the new EXPIRYINT attribute you can set on TSMODELS in CICS TS 4.2 ?
See http://publib.boulder.ibm.com/infocenter/cicsts/v4r2/topic/com.ibm.cics.ts.resourcedefinition.doc/resources/tsmodel/dfha4_attributes.html

This is the feature I would extended so that a specific time can be specified.

Say an application expects that its TSQs will be deleted at 17:00 hours.

You could calculate the expirary interval based on the normal start time and add it to the temporary storage model definition.

However should CICS be cycled for any reason, that expirary interval will be the time CICS starts back up and the delta from the normal start time.

Say CICS normally comes up at 09:00 and shuts down at 17:00 an expirary interval of 8 hours would be specified.

However if CICS came up again at 12:00, the TSQs would be deleted at 20:00, three hours later than expected.