CICS Extrapartiton TD Queue retention

[taylortek]

Hey all,
I have a program that creates a extrapartition TD Queue using the CICS CREATE TDQUEUE('xxxx') ATTRIBUTES(attrib-area). In the attribute area I am defining the dsname and ddname for th MVS dataset and a DIsposition of MOD to create if it does not already exist.
When I debug the program, I can see the dataset gets created in TSO/MVS but is not cataloged. When the program completes and the td queue is closed and disabled the td queue also is removed. If I create a dataset manually and catalog it, then do the same function as above, I retain the datset.
Am I missing an attribute in the create statement that will catalog the dataset on creation? Any help appreciated.

 

[stevexff]

Default retention action for a NEW dataset is DELETE,DELETE. So it looks like you need MOD,CATLG to make sure it gets kept, or even MOD,CATLG,CATLG to make sure it gets kept even if your region abends.

What are you writing to extrapartition TD, and how important is it? Extrapartition TD is not recoverable, and if you are writing a lot of it the QSAM I/O performance is terrible. Can't you find a better/safer/more efficient place to write it?

 

[taylortek]

Steve,

This original issue is the need to create and write an MVS dataset from within CICS. I was trying not to have to add an Assembler program to DYNALLOC the dataset. Even doing the create TDqueue with the MOD disp generates a (Mod,delete,delete), so once you close and disable the TDqueue, the dataset is deleted.

If you know of any other tricks of creating an MVS dataset and writing to it directly from CICS, please let me know. Submitting to the internal reader is not an option either in this installation..