ca.portal.admin

Re:Re: [IDMSVENDOR-L] Upgrading to Rel 17.0 this weekend, any

Discussion created by ca.portal.admin on Oct 28, 2010
helpful=
hints would be appreciated.

important to ask - what release are you upgrading FROM ???

Chris Hoelscher
IDMS/DB2 System & Database Architect
Humana Inc
502-476-2538
choelscher@humana.com

I refuse to repeat gossip - so listen carefully the first time






From:
""Timm, Edward"" <Edward.Timm@SALLIEMAE.COM>
To:
IDMSVENDOR-L@LISTSERV.IUASSN.COM
Date:
10/28/2010 01:43 PM
Subject:
[IDMSVENDOR-L] Upgrading to Rel 17.0 this weekend, any helpful
hints would be appreciated.
Sent by:
IDMS 3rd-party providers forum <IDMSVENDOR-L@LISTSERV.IUASSN.COM>



We are upgrading our Dev and QA environments to release 17 this weekend.
I=3D
have all APARS on up to October 7th.

Has anyone else upgraded to R17, and what problems did you encounter or
wha=3D
t items should we watch for.

Also would you be willing to briefly discuss their experiences with us.

Thanks you.

Edward Timm
Sr. Data Administrator - Technical Support
SallieMae Inc.
11100 USA Parkway
Fishers IN 46038
317-498-2887 (work cell)=3D20
317-596-1182 (office)
Edward.Timm@salliemae.com



The information transmitted is intended only for the person or entity to
wh=
ich 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.

This E-Mail has been scanned for viruses.



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: Upgrading to Rel 17.0 this weekend, any helpful hints would be appreciated."
"Do you have RO19996 applied?
If so, and you use the archive journals for anything, you may have issues.

It introduced a bug where the value in the block length field in the first =
block of an archive journal is out by 4. So anything that uses that field w=
ill have issues.

There is a test fix available from CA which corrects the problem (but you'd=
still have to manually fix any 'bad' archive journals).


Iain Robertson
BT Operate, Senior DBA
Telephone: +44 (0)20 8456 7108
Email: iain.dk.robertson@bt.com
=20
-----Original Message-----
From: IDMS Public Discussion Forum=20
[mailTo:IDMS-L@LISTSERV.IUASSN.COM] On Behalf Of Timm, Edward
Sent: 28 October 2010 18:43
To: IDMS-L@LISTSERV.IUASSN.COM
Subject: [IDMS-L] Upgrading to Rel 17.0 this weekend, any=20
helpful hints would be appreciated.
=20
We are upgrading our Dev and QA environments to release 17=20
this weekend. I have all APARS on up to October 7th.
=20
Has anyone else upgraded to R17, and what problems did you=20
encounter or what items should we watch for.
=20
Also would you be willing to briefly discuss their=20
experiences with us.
=20
Thanks you.
=20
Edward Timm
Sr. Data Administrator - Technical Support
SallieMae Inc.
11100 USA Parkway
Fishers IN 46038
317-498-2887 (work cell)=20
317-596-1182 (office)
Edward.Timm@salliemae.com
=
"
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: Upgrading to Rel 17.0 this weekend, any helpful hints would be appreciated."
"Do you have RO19996 applied?
If so, and you use the archive journals for anything, you may have issues.

It introduced a bug where the value in the block length field in the first block of an archive journal is out by 4. So anything that uses that field will have issues.

There is a test fix available from CA which corrects the problem (but you'd still have to manually fix any 'bad' archive journals).


Iain Robertson
BT Operate, Senior DBA
Telephone: +44 (0)20 8456 7108
Email: iain.dk.robertson@bt.com

-----Original Message-----
From: IDMS Public Discussion Forum
[mailTo:IDMS-L@LISTSERV.IUASSN.COM] On Behalf Of Timm, Edward
Sent: 28 October 2010 18:43
To: IDMS-L@LISTSERV.IUASSN.COM
Subject: [IDMS-L] Upgrading to Rel 17.0 this weekend, any
helpful hints would be appreciated.

We are upgrading our Dev and QA environments to release 17
this weekend. I have all APARS on up to October 7th.

Has anyone else upgraded to R17, and what problems did you
encounter or what items should we watch for.

Also would you be willing to briefly discuss their
experiences with us.

Thanks you.

Edward Timm
Sr. Data Administrator - Technical Support
SallieMae Inc.
11100 USA Parkway
Fishers IN 46038
317-498-2887 (work cell)
317-596-1182 (office)
Edward.Timm@salliemae.com
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: IDMS R17 installation
"Edward=2C=20
=20
Under z\OS I have converted a test and QA CV to R17 SP1 from R16 0701. No p=
roblems experienced. I have all the Hypers on and most other service which =
was available at the end of June 2010.=20
=20
I also have a test R17 SP1 CV running under zVSE. Has anyone gone live with=
IDMS R17 under zVSE?=20
=20
Nigel Salway =
"
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: IDMS R17 installation
"Edward,

Under z\OS I have converted a test and QA CV to R17 SP1 from R16 0701. No problems experienced. I have all the Hypers on and most other service which was available at the end of June 2010.

I also have a test R17 SP1 CV running under zVSE. Has anyone gone live with IDMS R17 under zVSE?

Nigel Salway
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
"Re: Upgrading to Rel 17.0 this weekend, any helpful hints would be appreciated."
"Iain=2C=20
=20
Can you provide more details on the issues with RO19996? When you say ""you =
use the archive journals for anything""=2C are you referring to user written=
programs or are you referring to IDMS functions which process the journals=
such as rollforward or extract?=20
=20
Sincerely=2C=20
=20
Nigel Salway
=20
Date: Fri=2C 29 Oct 2010 08:33:48 +0100
From: iain.dk.robertson@BT.COM
Subject: Re: Upgrading to Rel 17.0 this weekend=2C any helpful hints woul=
d be appreciated.
To: IDMS-L@LISTSERV.IUASSN.COM
=20
Do you have RO19996 applied?
If so=2C and you use the archive journals for anything=2C you may have is=
sues.
=20
It introduced a bug where the value in the block length field in the firs=
t block of an archive journal is out by 4. So anything that uses that field=
will have issues.
=20
There is a test fix available from CA which corrects the problem (but you=
'd still have to manually fix any 'bad' archive journals).
=20
=20
Iain Robertson
BT Operate=2C Senior DBA
Telephone: +44 (0)20 8456 7108
Email: iain.dk.robertson@bt.com
=20
=20
-----Original Message-----
From: IDMS Public Discussion Forum=20
[mailTo:IDMS-L@LISTSERV.IUASSN.COM] On Behalf Of Timm=2C Edward
Sent: 28 October 2010 18:43
To: IDMS-L@LISTSERV.IUASSN.COM
Subject: [IDMS-L] Upgrading to Rel 17.0 this weekend=2C any=20
helpful hints would be appreciated.
=20
We are upgrading our Dev and QA environments to release 17=20
this weekend. I have all APARS on up to October 7th.
=20
Has anyone else upgraded to R17=2C and what problems did you=20
encounter or what items should we watch for.
=20
Also would you be willing to briefly discuss their=20
experiences with us.
=20
Thanks you.
=20
Edward Timm
Sr. Data Administrator - Technical Support
SallieMae Inc.
11100 USA Parkway
Fishers IN 46038
317-498-2887 (work cell)=20
317-596-1182 (office)
Edward.Timm@salliemae.com
=20
=
"
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: Upgrading to Rel 17.0 this weekend, any helpful hints would be appreciated."
"Iain,

Can you provide more details on the issues with RO19996? When you say ""you use the archive journals for anything"", are you referring to user written programs or are you referring to IDMS functions which process the journals such as rollforward or extract?

Sincerely,

Nigel Salway
Date: Fri, 29 Oct 2010 08:33:48 +0100
From: iain.dk.robertson@BT.COM
Subject: Re: Upgrading to Rel 17.0 this weekend, any helpful hints would be appreciated.
To: IDMS-L@LISTSERV.IUASSN.COM

Do you have RO19996 applied?
If so, and you use the archive journals for anything, you may have issues.

It introduced a bug where the value in the block length field in the first block of an archive journal is out by 4. So anything that uses that field will have issues.

There is a test fix available from CA which corrects the problem (but you'd still have to manually fix any 'bad' archive journals).


Iain Robertson
BT Operate, Senior DBA
Telephone: +44 (0)20 8456 7108
Email: iain.dk.robertson@bt.com

-----Original Message-----
From: IDMS Public Discussion Forum
[mailTo:IDMS-L@LISTSERV.IUASSN.COM] On Behalf Of Timm, Edward
Sent: 28 October 2010 18:43
To: IDMS-L@LISTSERV.IUASSN.COM
Subject: [IDMS-L] Upgrading to Rel 17.0 this weekend, any
helpful hints would be appreciated.

We are upgrading our Dev and QA environments to release 17
this weekend. I have all APARS on up to October 7th.

Has anyone else upgraded to R17, and what problems did you
encounter or what items should we watch for.

Also would you be willing to briefly discuss their
experiences with us.

Thanks you.

Edward Timm
Sr. Data Administrator - Technical Support
SallieMae Inc.
11100 USA Parkway
Fishers IN 46038
317-498-2887 (work cell)
317-596-1182 (office)
Edward.Timm@salliemae.com
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
"Re: Upgrading to Rel 17.0 this weekend, any helpful hints would be appreciated."
"Nigel

We saw it first when we ran some archive journals through a third party pro=
duct.
This product assumed (not unreasonably) that the value in the block length=
field of each journal block was equal to the sum of the lengths of the ind=
ividual journal records +4. When it wasn't, the program failed complaining =
of sequence errors. Any program which assumes the value in the block length=
field will fail. We do have a few home written utilities which work that w=
ay, and they would all have failed with similar errors.

I've not done a lot of checking, but from what little I've tried rollforwar=
d and rollback seem OK. Best to check with CA if you're concerned, as the=
y should be able to provide a definitive answer.


Iain Robertson
BT Operate, Senior DBA
Telephone: +44 (0)20 8456 7108
Email: iain.dk.robertson@bt.com
=20
-----Original Message-----
From: IDMS Public Discussion Forum=20
On Behalf Of Nigel Salway
=20
Iain,=20
=20
Can you provide more details on the issues with RO19996? When=20
you say ""you use the archive journals for anything"", are you=20
referring to user written programs or are you referring to=20
IDMS functions which process the journals such as rollforward=20
or extract?=20
=20
Sincerely,=20
=20
Nigel Salway
=20
Date: Fri, 29 Oct 2010 08:33:48 +0100
From: iain.dk.robertson@BT.COM
Subject: Re: Upgrading to Rel 17.0 this weekend, any=20
helpful hints would be appreciated.
To: IDMS-L@LISTSERV.IUASSN.COM
=20
Do you have RO19996 applied?
If so, and you use the archive journals for anything, you=20
may have issues.
=20
It introduced a bug where the value in the block length=20
field in the first block of an archive journal is out by 4.=20
So anything that uses that field will have issues.
=20
There is a test fix available from CA which corrects the=20
problem (but you'd still have to manually fix any 'bad'=20
archive journals).
=20
=20
Iain Robertson
BT Operate, Senior DBA
Telephone: +44 (0)20 8456 7108
Email: iain.dk.robertson@bt.com
=20
=20
-----Original Message-----
From: IDMS Public Discussion Forum=20
[mailTo:IDMS-L@LISTSERV.IUASSN.COM] On Behalf Of Timm, Edward
Sent: 28 October 2010 18:43
To: IDMS-L@LISTSERV.IUASSN.COM
Subject: [IDMS-L] Upgrading to Rel 17.0 this weekend, any=20
helpful hints would be appreciated.
=20
We are upgrading our Dev and QA environments to release 17=20
this weekend. I have all APARS on up to October 7th.
=20
Has anyone else upgraded to R17, and what problems did you=20
encounter or what items should we watch for.
=20
Also would you be willing to briefly discuss their=20
experiences with us.
=20
Thanks you.
=20
Edward Timm
Sr. Data Administrator - Technical Support
SallieMae Inc.
11100 USA Parkway
Fishers IN 46038
317-498-2887 (work cell)=20
317-596-1182 (office)
Edward.Timm@salliemae.com
=20
=
"
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: Upgrading to Rel 17.0 this weekend, any helpful hints would be appreciated."
"Nigel

We saw it first when we ran some archive journals through a third party product.
This product assumed (not unreasonably) that the value in the block length field of each journal block was equal to the sum of the lengths of the individual journal records +4. When it wasn't, the program failed complaining of sequence errors. Any program which assumes the value in the block length field will fail. We do have a few home written utilities which work that way, and they would all have failed with similar errors.

I've not done a lot of checking, but from what little I've tried rollforward and rollback seem OK. Best to check with CA if you're concerned, as they should be able to provide a definitive answer.


Iain Robertson
BT Operate, Senior DBA
Telephone: +44 (0)20 8456 7108
Email: iain.dk.robertson@bt.com

-----Original Message-----
From: IDMS Public Discussion Forum
On Behalf Of Nigel Salway

Iain,

Can you provide more details on the issues with RO19996? When
you say ""you use the archive journals for anything"", are you
referring to user written programs or are you referring to
IDMS functions which process the journals such as rollforward
or extract?

Sincerely,

Nigel Salway
Date: Fri, 29 Oct 2010 08:33:48 +0100
From: iain.dk.robertson@BT.COM
Subject: Re: Upgrading to Rel 17.0 this weekend, any
helpful hints would be appreciated.
To: IDMS-L@LISTSERV.IUASSN.COM

Do you have RO19996 applied?
If so, and you use the archive journals for anything, you
may have issues.
It introduced a bug where the value in the block length
field in the first block of an archive journal is out by 4.
So anything that uses that field will have issues.
There is a test fix available from CA which corrects the
problem (but you'd still have to manually fix any 'bad'
archive journals).
Iain Robertson
BT Operate, Senior DBA
Telephone: +44 (0)20 8456 7108
Email: iain.dk.robertson@bt.com

-----Original Message-----
From: IDMS Public Discussion Forum
[mailTo:IDMS-L@LISTSERV.IUASSN.COM] On Behalf Of Timm, Edward
Sent: 28 October 2010 18:43
To: IDMS-L@LISTSERV.IUASSN.COM
Subject: [IDMS-L] Upgrading to Rel 17.0 this weekend, any
helpful hints would be appreciated.

We are upgrading our Dev and QA environments to release 17
this weekend. I have all APARS on up to October 7th.

Has anyone else upgraded to R17, and what problems did you
encounter or what items should we watch for.

Also would you be willing to briefly discuss their
experiences with us.

Thanks you.

Edward Timm
Sr. Data Administrator - Technical Support
SallieMae Inc.
11100 USA Parkway
Fishers IN 46038
317-498-2887 (work cell)
317-596-1182 (office)
Edward.Timm@salliemae.com
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
idms vs Z196
"just in case anyone is looking at the Z196 - i can happily report that we
rolled in Z196s to our test and prod datacenter over the weekend (we had
previously rolled into our dedicated DR site previously) and IDMS (17 SP1)
is living will with the Z196s


Chris Hoelscher
IDMS/DB2 System & Database Architect
Humana Inc
502-476-2538
choelscher@humana.com

I refuse to repeat gossip - so listen carefully the first time




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
idms vs Z196
"just in case anyone is looking at the Z196 - i can happily report that we
rolled in Z196s to our test and prod datacenter over the weekend (we had
previously rolled into our dedicated DR site previously) and IDMS (17 SP1)
is living will with the Z196s


Chris Hoelscher
IDMS/DB2 System & Database Architect
Humana Inc
502-476-2538
choelscher@humana.com

I refuse to repeat gossip - so listen carefully the first time




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: idms vs Z196
"Did you also get a zBX with it?

John T. Abell
President
International Software Products
Tel: 800-295-7608 Ext: 224
International: 1-416-593-5578 Ext: 224
Fax: 800-295-7609
International: 1-416-593-5579

E-mail: john.abell@intnlsoftwareproducts.com
Web: www.ispinfo.com

This email may contain confidential and privileged material for the sole use
of the intended recipient(s). Any review, use, retention, distribution or
disclosure by others is strictly prohibited. If you are not the intended
recipient (or authorized to receive on behalf of the named recipient),
please contact the sender by reply email and delete all copies of this
message. Also,email is susceptible to data corruption, interception,
tampering, unauthorized amendment and viruses. We only send and receive
emails on the basis that we are not liable for any such corruption,
interception, tampering, amendment or viruses or any consequence thereof.

Outcomes