Jerry, What your customer means to say is they have a COBOL module invoked by DB2 which runs in a WLM-managed stored procedure address space (SPAS).
There used to be a single SPAS per DB2 subsystem instance. It was the "environment" in which one or more stored procedures would be queued by DB2 as subtasks. Now one or more SPASes may be started by WLM and managed to a maximum number of subtasks each. When DB2 calls the procedure, WLM makes the decision as to which SPAS the request is queued and whether an additional SPAS is needed. The set of SPASes are known collectively as the "application environment." db -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Support, DUNNIT SYSTEMS LTD. Sent: Thursday, February 07, 2008 2:50 PM To: [email protected] Subject: Re: WLM for toddlers It's me, the guy who started this thread. I'm not actually sure I got an aswer to my original question. Maybe this will help. We have a customer who says they have a: "compiled/linked COBOL load module invoked from a DB2 sp that runs in the WLM address space." That's what I need to understand. Does the COBOL module actually run within the WLM address space? Or does it run in a separate started task and such started tasks are what the SPs run within? Or can it be both and, if so, what determines where the COBOL module runs? TIA, Jerry ---------------------------------------------------------------------- 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
