Migrating from v5 to v4 and back again

Luke G. Bauerlein

Migrating from v5 to v4 and back again
Attn: sysprogs. I migrated successfully from version4 to version 5 in my MVS "sandbox" LPAR. I now need to provide support for both versions in a development LPAR and then in production and not have to create 2 separate subsystems. I would like the ability to flip-flop them at will. I used the same logic when migrating from V3 to V4 and it worked fine.
When I tried to start version 4 in my sandbox I received an ABND=04e-00c90101 for DSNDBM1 and for DSNMSTR I received
DSNI012I - page logically broken
type 00000302
name dsndb06 .sysdbase.x'000027'
modname dsnimsms
erqual 0c10
I have looked up the message and am somewhat perplexed but my real question is : aside from authorizing the old v4 loadlibs and steplibing them do I need to change IEFSSNxx of parmlib ? I would like to use the same SSRC of "-" and the same subsystem name "dsn" in both versions. Copy ?
Luke Bauerlein
M&T Bank, Buffalo NY



Piontkowski Michael ML

Re: Migrating from v5 to v4 and back again
(in response to Luke G. Bauerlein)
Luke -

Falling back from V5 to V4 is well documented in the DB2 for OS/390
V5 Installation Guide (GC26-8970). At a minimum, V4 needs toleration
PTFs to handle the fallback.


Mike Piontkowski
Voice/Fax: 302.886.4612
mailto:[login to unmask email]

> ----------
> From: Luke G. Bauerlein[SMTP:[login to unmask email]
> Sent: Wednesday, January 05, 2000 1:28 PM
> To: [login to unmask email]
> Subject: [DB2-L] Migrating from v5 to v4 and back again
>
> Attn: sysprogs. I migrated successfully from version4 to version 5 in my
> MVS "sandbox" LPAR. I now need to provide support for both versions in a
> development LPAR and then in production and not have to create 2 separate
> subsystems. I would like the ability to flip-flop them at will. I used the
> same logic when migrating from V3 to V4 and it worked fine.
> When I tried to start version 4 in my sandbox I received an
> ABND=04e-00c90101 for DSNDBM1 and for DSNMSTR I received
> DSNI012I - page logically broken
> type 00000302
> name dsndb06 .sysdbase.x'000027'
> modname dsnimsms
> erqual 0c10
> I have looked up the message and am somewhat perplexed but my real
> question is : aside from authorizing the old v4 loadlibs and steplibing
> them do I need to change IEFSSNxx of parmlib ? I would like to use the
> same SSRC of "-" and the same subsystem name "dsn" in both versions. Copy
> ?
> Luke Bauerlein
> M&T Bank, Buffalo NY
>
>
>
> http://www.ryci.com/db2-l. The owners of the list can be reached at
> [login to unmask email]
>



Sue Janowitz

Re: Migrating from v5 to v4 and back again
(in response to Piontkowski Michael ML)
I'm the DB2 SYSADM at my company. I'm pretty sure we left the IEFSSN member
the same when we went from V4 to V5 (it's over a year ago now, so my memory
is a little fuzzy). I think the member name DSN3EPX changed from V3 to V4,
only that one time.

I would say check that you have the toleration (fall-back) PTFs on V4. And
that you follow the instructions on falling back. If you've used any new
features in V5, they may cause problems when you go back to version 4.

All disclaimers apply - my opinion only, this is not my company's official
word, etc.

Sue Janowitz
New England Financial Information Services
501 Boylston Street
Boston, MA 02116
email: [login to unmask email]
Phone: 617-578-2053


> -----Original Message-----
> From: Luke G. Bauerlein [SMTP:[login to unmask email]
> Sent: Wednesday, January 05, 2000 1:28 PM
> To: [login to unmask email]
> Subject: Migrating from v5 to v4 and back again
>
> Attn: sysprogs. I migrated successfully from version4 to version 5 in my
> MVS "sandbox" LPAR. I now need to provide support for both versions in a
> development LPAR and then in production and not have to create 2 separate
> subsystems. I would like the ability to flip-flop them at will. I used the
> same logic when migrating from V3 to V4 and it worked fine.
> When I tried to start version 4 in my sandbox I received an
> ABND=04e-00c90101 for DSNDBM1 and for DSNMSTR I received
> DSNI012I - page logically broken
> type 00000302
> name dsndb06 .sysdbase.x'000027'
> modname dsnimsms
> erqual 0c10
> I have looked up the message and am somewhat perplexed but my real
> question is : aside from authorizing the old v4 loadlibs and steplibing
> them do I need to change IEFSSNxx of parmlib ? I would like to use the
> same SSRC of "-" and the same subsystem name "dsn" in both versions. Copy
> ?
> Luke Bauerlein
> M&T Bank, Buffalo NY
>
>
>
> http://www.ryci.com/db2-l. The owners of the list can be reached at
> [login to unmask email]



Alexander Andrade

Re: Migrating from v5 to v4 and back again
(in response to Sue Janowitz)
I know in the case of concurrency, the DSN3EPX must be the latest version.
You can use the same SSID yes, as you will usually want the same for your
prod environment eg DSNP. During testing you probably had both versions
active at the same time with 2 different SSID's yes ?

Maybe the LPA members of PARMLIB need to be considered, as I believe some of
the DB2 modules have to be in LPA (please correct me if untrue) and you may
have to check you are IPL'ing with compatible db2 parmlib sets...... hope
this helps and dosent confuse.

Alex Andrade

Email : [login to unmask email] <mailto:[login to unmask email]>

-----Original Message-----
From: Sue Janowitz [SMTP:[login to unmask email]
Sent: Friday, January 07, 2000 1:10 PM
To: [login to unmask email]
Subject: Re: Migrating from v5 to v4 and back again

I'm the DB2 SYSADM at my company. I'm pretty sure we left the
IEFSSN member
the same when we went from V4 to V5 (it's over a year ago now, so my
memory
is a little fuzzy). I think the member name DSN3EPX changed from V3
to V4,
only that one time.

I would say check that you have the toleration (fall-back) PTFs on
V4. And
that you follow the instructions on falling back. If you've used
any new
features in V5, they may cause problems when you go back to version
4.

All disclaimers apply - my opinion only, this is not my company's
official
word, etc.

Sue Janowitz
New England Financial Information Services
501 Boylston Street
Boston, MA 02116
email: [login to unmask email]
Phone: 617-578-2053


> -----Original Message-----
> From: Luke G. Bauerlein [SMTP:[login to unmask email]
> Sent: Wednesday, January 05, 2000 1:28 PM
> To: [login to unmask email]
> Subject: Migrating from v5 to v4 and back again
>
> Attn: sysprogs. I migrated successfully from version4 to version
5 in my
> MVS "sandbox" LPAR. I now need to provide support for both
versions in a
> development LPAR and then in production and not have to create 2
separate
> subsystems. I would like the ability to flip-flop them at will. I
used the
> same logic when migrating from V3 to V4 and it worked fine.
> When I tried to start version 4 in my sandbox I received an
> ABND=04e-00c90101 for DSNDBM1 and for DSNMSTR I received
> DSNI012I - page logically broken
> type 00000302
> name dsndb06 .sysdbase.x'000027'
> modname dsnimsms
> erqual 0c10
> I have looked up the message and am somewhat perplexed but my real
> question is : aside from authorizing the old v4 loadlibs and
steplibing
> them do I need to change IEFSSNxx of parmlib ? I would like to
use the
> same SSRC of "-" and the same subsystem name "dsn" in both
versions. Copy
> ?
> Luke Bauerlein
> M&T Bank, Buffalo NY
>
> =======================To change your
subscription
>
> http://www.ryci.com/db2-l. The owners of the list can be reached
at
> [login to unmask email]




can



Luke G. Bauerlein

Re: Migrating from v5 to v4 and back again
(in response to Alexander Andrade)
The problem was corrected by applying PTF UQ31543 to V4, yet another migration/fallback PTF ( I had to apply over 200 for migration). Shame on me for being at 9702 of DB2 V4. We don't place any DB2 modules in LPA. I don't have to change IEFSSNxx but V5 must be the version of "early code" SDSNEXIT modules that are executed at subsystem startup time thus an IPL is required. SETSSI MVS command will not work with this particular subsystem , I tried (BOO HOO).
Thanks for the responses. Finding this professional listserver was a godsend.
Luke
>>> "Andrade, Alexander" <[login to unmask email]> 01/07/00 10:18AM >>>
I know in the case of concurrency, the DSN3EPX must be the latest version.
You can use the same SSID yes, as you will usually want the same for your
prod environment eg DSNP. During testing you probably had both versions
active at the same time with 2 different SSID's yes ?

Maybe the LPA members of PARMLIB need to be considered, as I believe some of
the DB2 modules have to be in LPA (please correct me if untrue) and you may
have to check you are IPL'ing with compatible db2 parmlib sets...... hope
this helps and dosent confuse.

Alex Andrade

Email : [login to unmask email] <mailto:[login to unmask email]>

-----Original Message-----
From: Sue Janowitz [SMTP:[login to unmask email]
Sent: Friday, January 07, 2000 1:10 PM
To: [login to unmask email]
Subject: Re: Migrating from v5 to v4 and back again

I'm the DB2 SYSADM at my company. I'm pretty sure we left the
IEFSSN member
the same when we went from V4 to V5 (it's over a year ago now, so my
memory
is a little fuzzy). I think the member name DSN3EPX changed from V3
to V4,
only that one time.

I would say check that you have the toleration (fall-back) PTFs on
V4. And
that you follow the instructions on falling back. If you've used
any new
features in V5, they may cause problems when you go back to version
4.

All disclaimers apply - my opinion only, this is not my company's
official
word, etc.

Sue Janowitz
New England Financial Information Services
501 Boylston Street
Boston, MA 02116
email: [login to unmask email]
Phone: 617-578-2053


> -----Original Message-----
> From: Luke G. Bauerlein [SMTP:[login to unmask email]
> Sent: Wednesday, January 05, 2000 1:28 PM
> To: [login to unmask email]
> Subject: Migrating from v5 to v4 and back again
>
> Attn: sysprogs. I migrated successfully from version4 to version
5 in my
> MVS "sandbox" LPAR. I now need to provide support for both
versions in a
> development LPAR and then in production and not have to create 2
separate
> subsystems. I would like the ability to flip-flop them at will. I
used the
> same logic when migrating from V3 to V4 and it worked fine.
> When I tried to start version 4 in my sandbox I received an
> ABND=04e-00c90101 for DSNDBM1 and for DSNMSTR I received
> DSNI012I - page logically broken
> type 00000302
> name dsndb06 .sysdbase.x'000027'
> modname dsnimsms
> erqual 0c10
> I have looked up the message and am somewhat perplexed but my real
> question is : aside from authorizing the old v4 loadlibs and
steplibing
> them do I need to change IEFSSNxx of parmlib ? I would like to
use the
> same SSRC of "-" and the same subsystem name "dsn" in both
versions. Copy
> ?
> Luke Bauerlein
> M&T Bank, Buffalo NY
>
> =======================To change your
subscription
>
> http://www.ryci.com/db2-l. The owners of the list can be reached
at
> [login to unmask email]




can