OS/390 DB2 and WLM Stored Procedures

David Booher

OS/390 DB2 and WLM Stored Procedures
Hello All,

My question pertains to the WLM Stored Procedure address space. I have a
WLM Application setup for running DSN1WLM in an address space. I can start
this address space manually and it stays up for about 5 minutes and then
terminates gracefully. I can't figure out how to get this address space to
start automatically when a DB2 Stored Procedure needs it. How is this
supposed to be "kicked off"? I can't seem to find anything in the manuals
besides the Environment variable which we have set to WLMENV1 and this
matches what is defined in WLM.

Thanks,
Dave Booher
Quest Software

Lee Hayden

Re: OS/390 DB2 and WLM Stored Procedures
(in response to David Booher)
I did not understand "Environment variable" as this applies to
OS/390. The WLM proc definition is in several places.

1. DB2: ZPARM (WLMENV in V6, n/a in V5)
2. OS/390: WLM environment definition
3. DB2: Each stored procedure definition (either a column in
sysibm.sysprocedures; V5
or sysibm.sysroutines; V6)

You can use SQL to check the DB2 definitions: Here is a sample
operator command to check the OS/390 part:

D WLM,APPLENV=DB2TWLM1

(output)
IWM029I 08.13.58 WLM DISPLAY 067
APPLICATION ENVIRONMENT NAME STATE STATE DATA
DB2TWLM1 AVAILABLE
ATTRIBUTES: PROC=DB2TWLM1 SUBSYSTEM TYPE: DB2


I hope this helps.


-----Original Message-----
From: David Booher [mailto:[login to unmask email]
Sent: Wednesday, December 20, 2000 3:54 PM
Subject: OS/390 DB2 and WLM Stored Procedures



Hello All,

My question pertains to the WLM Stored Procedure address space. I have a
WLM Application setup for running DSN1WLM in an address space. I can start
this address space manually and it stays up for about 5 minutes and then
terminates gracefully. I can't figure out how to get this address space to
start automatically when a DB2 Stored Procedure needs it. How is this
supposed to be "kicked off"? I can't seem to find anything in the manuals
besides the Environment variable which we have set to WLMENV1 and this
matches what is defined in WLM.

Thanks,
Dave Booher
Quest Software



David Booher

Re: OS/390 DB2 and WLM Stored Procedures
(in response to Lee Hayden)
I discovered the answer to my problem later last evening. I did a D
WLM,APPLENV=WLMENV1 and discovered it in a STOPPED state. Apparently, this
occurred when I was testing the JCL for the address space and the STOPPED
state appears to have carried-over thru multiple IPLs. Once a VARY
WLM,APPLENV=WLMENV1,RESUME was issued, everything appears to be OK.

Dave Booher
Systems Programmer
Quest Software


-----Original Message-----
From: Hayden, Lee [mailto:[login to unmask email]
Sent: Thursday, December 21, 2000 7:20 AM
To: [login to unmask email]
Subject: Re: OS/390 DB2 and WLM Stored Procedures


I did not understand "Environment variable" as this applies to
OS/390. The WLM proc definition is in several places.

1. DB2: ZPARM (WLMENV in V6, n/a in V5)
2. OS/390: WLM environment definition
3. DB2: Each stored procedure definition (either a column in
sysibm.sysprocedures; V5
or sysibm.sysroutines; V6)

You can use SQL to check the DB2 definitions: Here is a sample
operator command to check the OS/390 part:

D WLM,APPLENV=DB2TWLM1

(output)
IWM029I 08.13.58 WLM DISPLAY 067
APPLICATION ENVIRONMENT NAME STATE STATE DATA
DB2TWLM1 AVAILABLE
ATTRIBUTES: PROC=DB2TWLM1 SUBSYSTEM TYPE: DB2


I hope this helps.


-----Original Message-----
From: David Booher [mailto:[login to unmask email]
Sent: Wednesday, December 20, 2000 3:54 PM
Subject: OS/390 DB2 and WLM Stored Procedures



Hello All,

My question pertains to the WLM Stored Procedure address space. I have a
WLM Application setup for running DSN1WLM in an address space. I can start
this address space manually and it stays up for about 5 minutes and then
terminates gracefully. I can't figure out how to get this address space to
start automatically when a DB2 Stored Procedure needs it. How is this
supposed to be "kicked off"? I can't seem to find anything in the manuals
besides the Environment variable which we have set to WLMENV1 and this
matches what is defined in WLM.

Thanks,
Dave Booher
Quest Software