I'm afraid You are right. But this is silly. I would never get the authority to submit my own msg region. Besides, the main problem would not exist if Debug Tool released the dataset at termination. I can't understand why they keep the allocation at all.
If the FREE command supported datasetname I could use the AT TERMINATION command for this, but it seems not to. BTW, typically for IBM's new products, they didn't even document this command correctly in the reference manual, it just says: "The FREE command frees a file that is currently allocated. ddname Name of the file to free." In reality You have to use the "FREE FILE ddname" format to get it working! As it is, the IMS region keeps the exclusive allocation of my save dataset "eternally" or until the region itself terminate. Sigh! Regards, Thomas Berg _________________________________________ Thomas Berg Specialist A M SWEDBANK > -----Ursprungligt meddelande----- > Från: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] För > Brian Peterson > Skickat: den 15 februari 2010 19:49 > Till: IBM-MAIN@bama.ua.edu > Ämne: Re: Debug Tool problem > > I believe you must run your IMS MPP in a single message region. Which > message region(s) are eligible to run a particular IMS MPP program is > defined by the IMS sysprog who assigns IMS transactions to classes, and > classes to regions, as I understand it. > > The following quotation from "Debug Tool for z/OS Users Guide" topic 6.3.4 > "Creating setup file for your IMS program by using Debug Tool Utilities" > reads to me like a technical writer has tried to beautify/spin the > absolute > requirement that Debug Tool IMS MPP testing must be done in a single > region > with pretty words making it sound like this is somehow optional (but still > a > good idea). > > "You can also create and customize a setup file to create a private > message > region that you can use to test your IMS message processing program (MPP). > Creating a private message region with class X allows you to test your IMS > program run by transaction X and reduce the risk of interfering with other > regions being used by other IMS programs." > > Brian > > On Mon, 15 Feb 2010 16:44:59 +0100, Thomas Berg wrote: > > >Hi, > > > >I have a problem with Debug Tool that I can't resolve (at least by > myself...). > >When using it at debugging an IMS program (within IMS!) my save dataset > will > >be in exclusive hold in the actual IMS region. > >The problem arises when I run the same program (e g by responding to the > screen) > >and it is started in *another* region. Now the saved (e g) breakpoints > can't be > >loaded because the save dataset is hold by the first region. > > > >Does someone have a solution for this ? (That do not include e g another > config > >of IMS etc.) > > > >TIA! > > > >Regards, > >Thomas Berg > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
