Using MXI, I decided to to a little experiment.  I started a DB2 subsystem
then stopped it.  Looking at the MDQ screen (thanks Rob) I see the
following:
Jobname  ASID     To   From XMSE     ASCB     Type CJOB     CAID Status

DW7EDIST 004C      0      1 7FFA4E20          From RRS      0034 Active

DW7EDBM1 004B      0      1 7FFA4BE0          From RRS      0034 Active

DW7EIRLM 004A      *      * 7FFA4558          Both *        *    System LX

DW7EMSTR 0049      0      1 7FFA5BE0          From RRS      0034 Active


Which shows that both the System LX (in the case of the IRLM) note that IRLM
was started PC=NO, the default.  In addition, it shows that this address
space had, at the time of shutdown, a linkage FROM the RRS address space.
However, looking at the XM display in MXI, I see that RRS owns a SYSTEM LX,
so stopping RRS will most likely NOT release that connection.  This is a DB2
v7 subsystem, and I don't know if DB2 v8 had any changes to communicate with
RRS at DB2 shutdown to reduce the amount of unavailable ASN's.
Wayne Driscoll
Product Developer
Western Metal Supply
NOTE: All opinions are strictly my own.
 
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Jim Mulder
Sent: Thursday, July 21, 2005 3:24 PM
To: [email protected]
Subject: Re: RSVNONR -DB2

IBM Mainframe Discussion List <[email protected]> wrote on 07/21/2005
08:35:27 AM:

> Check the archives.  This is WAD.  DB2 uses cross memory services to 
> operate, and in order to reduce the number of resources it uses, at 
> subsystem initialization, it issues an SRB into the MASTER address 
> space
to
> allocate the system LX's.  Because of this, when DB2 subsystems
shutdown,
> the ASN's are marked as non-reusable because there is a XM linkage
between
> ASN 1 and the DB2 ASN's.  (I am not sure if the ASN reuse code in z/OS
1.6
> changes this, maybe Peter Relson could comment). 
> The best way to avoid this situation is to NOT recycle DB2 regions.  I
see
> little reason why DB2 has to be stopped during the lifetime of an IPL. 
> 
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf
> Of William Ball
> Sent: Thursday, July 21, 2005 7:18 AM
> To: [email protected]
> Subject: RSVNONR -DB2
> 
> All,
> 
> I understand why RSVNONR is in a "bit of a fix" <g> in our shop and
we're
> trying to address the problem by getting the problem tasks to shutdown
> -cleanly- but aren't having much luck so I thought I'd run it up the
flag
> pole (so to speak) and see if any of you have found a solution or 
> might suggest one.
> 
> The -offending- address spaces are -all- DB2 regions that get cycled 
> on
a
> regular basis (I still need to talk to the DBA to see why). We've got 
> Landmark and BMC as well as CICS that -touch- DB2 and we've tryed
shutting
> them down in about everyway possible but the IEF352I message won't go
away
> and of course the used RSVNONR keeps increasing with every shutdown 
> and startup of DB2.
> 
> It's been 2.5 months since an IPL and we plan on increasing RSVNONR 
> from
> 99 to 2xx but it just urks me to think we might -have- to have planned
IPL's
> over something this silly. Has anyone found a way around it or do you
all
> just plan an IPL on some scheduled basis and call it a day? 

  Currently, any asid which uses a system LX is permanently non-reusuable,
and that is likely what you are seeing with DB2.  The only thing you can do
at this time is avoid recycling DB2. 

  The ASN reuse facility will be the eventual solution to this problem.
Although most of the z/OS BCP plumbing is in z/OS 1.6 and the machine
support is in the z890 and z990 machines, there is still more software work
to be done (some in z/OS, some in other IBM products, probably some in ISV
products, and possibly some in your own (installation specific) programs.
The earliest that this might be available would be the next release after
z/OS 1.7. 
 
Jim Mulder   z/OS System Test   IBM Corp.  Poughkeepsie,  NY

----------------------------------------------------------------------
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

----------------------------------------------------------------------
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

Reply via email to