2009/5/27 Ward, Mike S <[email protected]>: > I investigated the Storage macro and it seems to work just like the > getmain and freemain macros. If you have any expertise in selecting > persistent storage, I'm more than happy to listen. It seems there are 4 > types of storage. Task, job step, address space, and system. I was > thinking that job step storage would be a good candidate, but I'm not > sure of how to code that request in a Storage obtain. Would you have any > hints in this area?
Storage association to a task is generally controlled by subpool. Subpools 131 and 132 are jobstep-TCB associated, and can be used by non-authorized programs. You can request a subpool on either GETMAIN or STORAGE OBTAIN. I know nothing of the MQ environment, but it is common for various subpools to be shared with subtasks; e.g. in a batch job, by default all ATTACHed tasks will share subpool 0, whereas in TSO subpool 0 is not shared between the Terminal Monitor Program (TMP) and the attached TSO commands, but subpool 78 is. If you obtain storage from a subpool that is owned by a task (jobstep or not) that isn't going to go away for the life of your repeated exit invocations (even if your taks does), then you should be fine. Probably the arrangements for subpool use and sharing in MQ are documented somewhere. If they are not, you can figure out a lot of what goes on by looking at a dump. Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
