ca.portal.admin

Re:Re: Downward Migration

Discussion created by ca.portal.admin on Aug 28, 2009
Bill,

I presume you're talking about dialogs and maps that have been recompiled on
R16SP7. I doubt this would be possible. If it were, it would pre-suppose
that there had been no structural changes to the ADS or Mapping runtime
environments since R15SP2. But, if the programmers didn't use anything at
all from releases greater than R15SP2, they may run.

Bob Wiklund
Tiburon Technologies
623 594-6022

________________________________

From: IDMS 3rd-party providers forum on behalf of William M. Allen, Jr.
Sent: Fri 8/28/2009 11:56 AM
To: IDMSVENDOR-L@LISTSERV.IUASSN.COM
Subject: Downward Migration



Hello All:



Is anyone aware of any issues with running IDMS 16.0 SP7 Dialogs or Maps on
a 15.0 SP2 IDMS Region?



This particular Client only does load module migrations; there is no source
code in the production region.



William M. Allen, Jr.

ARCH Consulting Associates, Ltd.

(704) 641-0296

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Backward Migration is Possible with Optional APAR
"Hello All:



Many thanks to Mr. Thomas Schoenborn for the information on Backward
Compatibility from 16 to 15.



It can be done, there is a CA Informational APAR available number QI80754
that explains it quite well.



All that is required is to turn on Optional bit 251 in the Optional APAR
module (RHDCOPTF).



William M. Allen, Jr.

ARCH Consulting Associates, Ltd.

(704) 641-0296
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Backward Migration is Possible with Optional APAR
"Hello All:



Many thanks to Mr. Thomas Schoenborn for the information on Backward
Compatibility from 16 to 15.



It can be done, there is a CA Informational APAR available number QI80754
that explains it quite well.



All that is required is to turn on Optional bit 251 in the Optional APAR
module (RHDCOPTF).



William M. Allen, Jr.

ARCH Consulting Associates, Ltd.

(704) 641-0296
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Release 16.0 or 17.0
"Good morning everybody,

Our site is in the process of upgrading the mainframe system software. =
We
will be on CICS TS 2.3 in a few days and ZOS 1.7 by the end of Septemb=
er.
Their original plan calls for me to upgrade IDMS from Release 15.0 to 1=
6.0.
I'm thinking of attempting to convince them to just go straight to 17.0=
.
I'm certain that this can be done and after a few discussions with IDMS=

gurus a month or so ago, it sounds like both 16.0 and 17.0 upgrades are=
not
the beasts that upgrading to 12.0 was. More like the 12.0 or 12.01 upgr=
ade
to 14.0 or 14.1.

Can anyone think of any reason to NOT simply upgrade from Release 15.0 =
to
17.0? We use CICS as a front end and ACF2. Pretty vanilla as far as I c=
an
see.

The shop has pretty heavy IDMS usage but no new IDMS development. Nor d=
o
they have any plans to re-platform their IDMS legacy apps to server wor=
ld
or retire the mainframe. Conversely some of the new features of Release=

16.0 or 17.0 most likely will not get implemented any time soon.

On a side note, the abends occurring in the CICS TS 2.3 IDMS/CICS inter=
face
modules were corrected by re-assembling and re-linking the interface
modules using the more recent CICS TS 2.3 macro library. No APAR's wer=
e
necessary. Thanks to Bill Allen for his help.

Thanks

Tim Kupin
IDMS DBA
IBM Global Services

office 864.609.3564
cell 301.752.6857
home office 301.638.7424
timkupin@us.ibm.com
tim_kupin@comcast.net=
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Release 16.0 or 17.0
"Good morning everybody,

Our site is in the process of upgrading the mainframe system software. We
will be on CICS TS 2.3 in a few days and ZOS 1.7 by the end of September.
Their original plan calls for me to upgrade IDMS from Release 15.0 to 16.0.
I'm thinking of attempting to convince them to just go straight to 17.0.
I'm certain that this can be done and after a few discussions with IDMS
gurus a month or so ago, it sounds like both 16.0 and 17.0 upgrades are not
the beasts that upgrading to 12.0 was. More like the 12.0 or 12.01 upgrade
to 14.0 or 14.1.

Can anyone think of any reason to NOT simply upgrade from Release 15.0 to
17.0? We use CICS as a front end and ACF2. Pretty vanilla as far as I can
see.

The shop has pretty heavy IDMS usage but no new IDMS development. Nor do
they have any plans to re-platform their IDMS legacy apps to server world
or retire the mainframe. Conversely some of the new features of Release
16.0 or 17.0 most likely will not get implemented any time soon.

On a side note, the abends occurring in the CICS TS 2.3 IDMS/CICS interface
modules were corrected by re-assembling and re-linking the interface
modules using the more recent CICS TS 2.3 macro library. No APAR's were
necessary. Thanks to Bill Allen for his help.

Thanks

Tim Kupin
IDMS DBA
IBM Global Services

office 864.609.3564
cell 301.752.6857
home office 301.638.7424
timkupin@us.ibm.com
tim_kupin@comcast.net
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Release 16.0 or 17.0
"we were faced with the same dilema when we became aware of 17.0 - we chose
to go the 17.0 route

you will hit many many changes going from 15 to either one - many of the
snags we hit (CICS, 2-phase commit, etc) we would have hit either way

the ziip explotiation made the choice (for us) a ""no-brainer"" (which is
why they let me put it in)

i know of no reason NOT to go to 17 - based on how long releases stick
around, you MIGHT be able to avoid another full release upgrade for 5-6
years ... but your milage may differ




Chris Hoelscher
Senior IDMS & DB2 Database Administrator
Humana Inc
502-476-2538
choelscher@humana.com

you only need to test the programs that you want to work correctly






From:
Tim Kupin <timkupin@US.IBM.COM>
To:
IDMSVENDOR-L@LISTSERV.IUASSN.COM
Date:
08/31/2009 12:02
Subject:
[IDMSVENDOR-L] Release 16.0 or 17.0
Sent by:
IDMS 3rd-party providers forum <IDMSVENDOR-L@LISTSERV.IUASSN.COM>



Good morning everybody,

Our site is in the process of upgrading the mainframe system software. =
We
will be on CICS TS 2.3 in a few days and ZOS 1.7 by the end of Septemb=
er.
Their original plan calls for me to upgrade IDMS from Release 15.0 to 1=
6.0.
I'm thinking of attempting to convince them to just go straight to 17.0=
.
I'm certain that this can be done and after a few discussions with IDMS=

gurus a month or so ago, it sounds like both 16.0 and 17.0 upgrades are=
not
the beasts that upgrading to 12.0 was. More like the 12.0 or 12.01 upgr=
ade
to 14.0 or 14.1.

Can anyone think of any reason to NOT simply upgrade from Release 15.0 =
to
17.0? We use CICS as a front end and ACF2. Pretty vanilla as far as I c=
an
see.

The shop has pretty heavy IDMS usage but no new IDMS development. Nor d=
o
they have any plans to re-platform their IDMS legacy apps to server wor=
ld
or retire the mainframe. Conversely some of the new features of Release=

16.0 or 17.0 most likely will not get implemented any time soon.

On a side note, the abends occurring in the CICS TS 2.3 IDMS/CICS inter=
face
modules were corrected by re-assembling and re-linking the interface
modules using the more recent CICS TS 2.3 macro library. No APAR's wer=
e
necessary. Thanks to Bill Allen for his help.

Thanks

Tim Kupin
IDMS DBA
IBM Global Services

office 864.609.3564
cell 301.752.6857
home office 301.638.7424
timkupin@us.ibm.com
tim_kupin@comcast.net=



The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: [IDMSVENDOR-L] Release 16.0 or 17.0
"we were faced with the same dilema when we became aware of 17.0 - we chose
to go the 17.0 route

you will hit many many changes going from 15 to either one - many of the
snags we hit (CICS, 2-phase commit, etc) we would have hit either way

the ziip explotiation made the choice (for us) a ""no-brainer"" (which is
why they let me put it in)

i know of no reason NOT to go to 17 - based on how long releases stick
around, you MIGHT be able to avoid another full release upgrade for 5-6
years ... but your milage may differ




Chris Hoelscher
Senior IDMS & DB2 Database Administrator
Humana Inc
502-476-2538
choelscher@humana.com

you only need to test the programs that you want to work correctly






From:
Tim Kupin <timkupin@US.IBM.COM>
To:
IDMSVENDOR-L@LISTSERV.IUASSN.COM
Date:
08/31/2009 12:02
Subject:
[IDMSVENDOR-L] Release 16.0 or 17.0
Sent by:
IDMS 3rd-party providers forum <IDMSVENDOR-L@LISTSERV.IUASSN.COM>



Good morning everybody,

Our site is in the process of upgrading the mainframe system software. =
We
will be on CICS TS 2.3 in a few days and ZOS 1.7 by the end of Septemb=
er.
Their original plan calls for me to upgrade IDMS from Release 15.0 to 1=
6.0.
I'm thinking of attempting to convince them to just go straight to 17.0=
.
I'm certain that this can be done and after a few discussions with IDMS=

gurus a month or so ago, it sounds like both 16.0 and 17.0 upgrades are=
not
the beasts that upgrading to 12.0 was. More like the 12.0 or 12.01 upgr=
ade
to 14.0 or 14.1.

Can anyone think of any reason to NOT simply upgrade from Release 15.0 =
to
17.0? We use CICS as a front end and ACF2. Pretty vanilla as far as I c=
an
see.

The shop has pretty heavy IDMS usage but no new IDMS development. Nor d=
o
they have any plans to re-platform their IDMS legacy apps to server wor=
ld
or retire the mainframe. Conversely some of the new features of Release=

16.0 or 17.0 most likely will not get implemented any time soon.

On a side note, the abends occurring in the CICS TS 2.3 IDMS/CICS inter=
face
modules were corrected by re-assembling and re-linking the interface
modules using the more recent CICS TS 2.3 macro library. No APAR's wer=
e
necessary. Thanks to Bill Allen for his help.

Thanks

Tim Kupin
IDMS DBA
IBM Global Services

office 864.609.3564
cell 301.752.6857
home office 301.638.7424
timkupin@us.ibm.com
tim_kupin@comcast.net=



The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Release 16.0 or 17.0
"Tim,

You don't seem too worried running under out of support software, if you ar=
e just hitting z/OS 1.7, but I would expect IDMS 16 to be supported for pos=
sibly another 2 years or so making 17 a better bet.

Chris Wood
Alberta Department of Energy
CANADA =20

Outcomes