z/OS DB2 V7.1: Disabling DB2 establishes stored procedure address space

Raquel Rodriguez

z/OS DB2 V7.1: Disabling DB2 establishes stored procedure address space
We have changed DB2 established stored procedures to
WLM procedures and hence, I now need to ‘remove’
DB2TSPAS from the ZPARM.

When I run DSNTINST, on panel DSNTIPB (which is the
main panel from where we choose various options), I
choose option “28 ROUTINE PARAMETERS”. This throws up
the following screen:

Enter data below:

* 1 WLM PROC NAME ===> DB2TWLM WLM-established
stored procedure JCL PROC

* 2 DB2 PROC NAME ===> DB2TSPAS DB2-established
stored procedure JCL PROC

3 NUMBER OF TCBS ===> 8 Number of
concurrent TCBs (1-100)

4 MAX ABEND COUNT ===> 2 Allowable ABENDs
for a procedure (0-255)

5 TIMEOUT VALUE ===> 180 Seconds to wait
before SQL CALL or

function
invocation fails (5-1800,NOLIMIT)

6 WLM ENVIRONMENT ===> Default
WLM environment name


As can be seen, the field “DB2 PROC NAME”, which I
want to blank out, is protected, so I cannot blank it
out here. So, what are my options?


If I directly go into corresponding DSNTIJUZ and
DSNTID*A members and blank out STORPROC value (which
is what DB2 PROC NAME finally translates to), and then
compile DNSTIJUZ to create new ZPARM, could there be a
problem?

TIA
Raquel.

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Raquel Rodriguez

Re: z/OS DB2 V7.1: Disabling DB2 establishes stored procedure address space
(in response to Raquel Rodriguez)
Request someone to reply to this since this is kinda
urgent...

We have changed DB2 established stored procedures to
WLM procedures and hence, I now need to 'remove'
DB2TSPAS from the ZPARM.

When I run DSNTINST, on panel DSNTIPB (which is the
main panel from where we choose various options), I
choose option "28 ROUTINE PARAMETERS". This throws
up the following screen:


Enter data below:

* 1 WLM PROC NAME === DB2TWLM WLM-established
stored procedure JCL PROC

* 2 DB2 PROC NAME === DB2TSPAS DB2-established
stored procedure JCL PROC

3 NUMBER OF TCBS === 8 Number of
concurrent TCBs
(1-100)

4 MAX ABEND COUNT === 2 Allowable
ABENDs for a
procedure (0-255)

5 TIMEOUT VALUE === 180 Seconds to wait
before
SQL CALL or function invocation fails
(5-1800,NOLIMIT)

6 WLM ENVIRONMENT === Default WLM
environment
name


As can be seen, the field "DB2 PROC NAME", which I
want to blank out, is protected, so I cannot blank
it out here.
So, what are my options?

If I directly go into corresponding DSNTIJUZ and
DSNTID*A members and blank out STORPROC value (which
is what
DB2 PROC NAME finally translates to), and then
compile DNSTIJUZ
to create new ZPARM, will there be a problem?

TIA
Raquel.

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Richard Clark

Re: z/OS DB2 V7.1: Disabling DB2 establishes stored procedure address space
(in response to Raquel Rodriguez)
Raquel - the Installation Guide seems to imply it is OK to do this. If you cannot edit using the install panels - then your only
choice is to update DSNTIJUZ directly.

The doc. says to replace the values with blanks.....
if you do this you get a warning when you assemble the zparm :
STORPROC= , gives the warning.

change it to :
STORPROC=,
and you get a clean assemble .

Here is the clip from the Intallation Guide :

2. DB2 PROC NAME
Acceptable values: 1-8 alphanumeric characters
Default: ssnSPAS
DSNZPxxx: DSN6SYSP STORPROC
Specify a name for the JCL procedure that is used to start the DB2-established
address space. If you replace the default value with blanks, you cannot start the
DB2-established stored procedures address space until you update the subsystem
parameter. In addition, you cannot edit the stored procedures sample jobs,
DSNTEJ6S, DSNTEJ6P, DSNTEJ6T, DSNTEJ6D, DSNTEJ63, DSNTEJ64, and
DSNTEJ65.

I tried this on a test subsystem - with the clean assemble - (v7.1) and it started OK - no SPAS came up with the other tasks.
I think you'll be OK.....

Richard


-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On Behalf Of Raquel Rodriguez
Sent: Thursday, December 15, 2005 3:29 AM
To: [login to unmask email]
Subject: Re: [DB2-L] z/OS DB2 V7.1: Disabling DB2 establishes stored procedure address space


Request someone to reply to this since this is kinda
urgent...

We have changed DB2 established stored procedures to
WLM procedures and hence, I now need to 'remove'
DB2TSPAS from the ZPARM.

When I run DSNTINST, on panel DSNTIPB (which is the
main panel from where we choose various options), I
choose option "28 ROUTINE PARAMETERS". This throws
up the following screen:


Enter data below:

* 1 WLM PROC NAME === DB2TWLM WLM-established
stored procedure JCL PROC

* 2 DB2 PROC NAME === DB2TSPAS DB2-established
stored procedure JCL PROC

3 NUMBER OF TCBS === 8 Number of
concurrent TCBs
(1-100)

4 MAX ABEND COUNT === 2 Allowable
ABENDs for a
procedure (0-255)

5 TIMEOUT VALUE === 180 Seconds to wait
before
SQL CALL or function invocation fails
(5-1800,NOLIMIT)

6 WLM ENVIRONMENT === Default WLM
environment
name


As can be seen, the field "DB2 PROC NAME", which I
want to blank out, is protected, so I cannot blank
it out here.
So, what are my options?

If I directly go into corresponding DSNTIJUZ and
DSNTID*A members and blank out STORPROC value (which
is what
DB2 PROC NAME finally translates to), and then
compile DNSTIJUZ
to create new ZPARM, will there be a problem?

TIA
Raquel.

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html.
From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be
reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

-----------------------------------------
CONFIDENTIALITY NOTE: This e-mail message, including any attachment(s),
contains information that may be confidential, protected by the
attorney-client or other legal privileges, and/or proprietary non-
public information. If you are not an intended recipient of this
message or an authorized assistant to an intended recipient, please
notify the sender by replying to this message and then delete it from
your system. Use, dissemination, distribution, or reproduction of this
message and/or any of its attachments (if any) by unintended recipients
is not authorized and may be unlawful.


---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm