ca.portal.admin

Re: Goodbye 14.0

Discussion created by ca.portal.admin on Sep 30, 2005
Here is a question for the list,,,,,, how many sites have moved off
of IDMS in the last 5 years?

Jerry Fica

At 12:23 PM 9/30/2005, you wrote:
I upgraded the production CVs to R16.0 tape SP1 on Labor Day weekend. All
the TEST/QA CVs had previously upgraded. Prior to the upgrade we were
running R14.0.

Regards,

John Collins
SAIC
858-826-3463


-----Original Message-----
From: IDMS Public Discussion Forum [mailTo:IDMS-L@LISTSERV.IUASSN.COM] On
Behalf Of George H Lewandowski
Sent: Friday, September 30, 2005 12:01 PM
To: IDMS-L@LISTSERV.IUASSN.COM
Subject: Re: goodbye 14.1

We are just completing converting to 15.0.... 14.1 has left the
building....

George Lewandowski
Database Administrator - High Availability Database Support
GTS Database Engineering
Abbott Laboratories
GB17, J46-2E
(847) 938-5526
george.lewandowski@abbott.com




""Verinder, Gene"" <GVERINDE@ALLDATA.NET>
Sent by: IDMS Public Discussion Forum <IDMS-L@LISTSERV.IUASSN.COM>
09/30/2005 01:55 PM
Please respond to IDMS Public Discussion Forum


To: IDMS-L@LISTSERV.IUASSN.COM
cc:
Subject: Re: goodbye 14.1


Still on 14.1 but 16.0 looms around the corner.

________________________________

From: IDMS Public Discussion Forum on behalf of Alan Fields
Sent: Fri 9/30/2005 12:22 PM
To: IDMS-L@LISTSERV.IUASSN.COM
Subject: Re: goodbye 14.1



14.1 is dead. Long live 14.1!

And for those of us who haven't upgraded yet, I have a quick survey. By
show of e-mails, how many are still running 14.x and how many are still
running, um, er older versions?

Alan Fields


IDMS Public Discussion Forum <IDMS-L@LISTSERV.IUASSN.COM> wrote on
09/30/2005 12:43:59 PM:
good-bye 14.1
Chris Hoelscher
IDMS & DB2 Database Administrator
Humana Inc
502-580-2538
choelscher@humana.com
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
Verifying an IDMS Install
"Hi All,
Management here is once again on a mission to have documentation produced
on how a product is verified once it's installed.
I would like to query the list to find out how you (if you are the
installer) verifies that IDMS has been installed correctly and ALL the
components are working.
In my case, I have to install every IDMS product - both base and tool. I
have no way, that I know of, that I could possibly test that every component
is working, especially when I'm in an environment where not all products are
utilized by clients. There are a lot of products within the IDMS family
that I I don't know how to use, or can not test because I simply don't have
the resources (database and/or application). This is especially true since
I initially install products into an LPAR that is only used by system
programmers.
I have always installed IDMS and tested that regions come up with no
problems, CICS/TSO/VTAM interfaces are working, and the basic compilers work
- IDD, SSC, etc. Beyond that, I install into test regions with a quick
backout plan readily available. It's worked for me for over 15 years.

Joe Lupico
IDMS System Support
""Our World is a Happy World""

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








Normal

Normal
IDMS release 16.0 Installation issue
"Hello Everyone:

This is meant as a heads up to everyone in the process of installing IDMS
Release 16.0 SP2.

We received a 3964 during startup. In contacting CA for support on Saturday
it was learned that the System Generation Parameter STACKSIZE needed to be
increased. CA recommended a value of 3000, our initial value was 1024,
apparently 1024 was not enough to allow for startup. Once the sysgen change was made
and the stack size increased the system started with no problems.

This issue was not documented in the cover letter that came with the
installation tape.

I would recommend that you change this value in all your current systems
that you are planning to convert to IDMS 16.0 SP2 to avoid this issue.

Bill Allen
ARCH Consulting Associates, Ltd.

"
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 release 16.0 Installation issue
"Bill,
We ran into the same problem when we went from 14.1 to 15.0. I think this is covered in the 15.0 release guide.

-----Original Message-----
From: IDMS 3rd-party providers forum [mailTo:IDMSVENDOR-L@LISTSERV.IUASSN.COM] On Behalf Of Bill Allen
Sent: Monday, October 10, 2005 1:14 PM
To: IDMSVENDOR-L@LISTSERV.IUASSN.COM
Subject: IDMS release 16.0 Installation issue

Hello Everyone:

This is meant as a heads up to everyone in the process of installing IDMS
Release 16.0 SP2.

We received a 3964 during startup. In contacting CA for support on Saturday
it was learned that the System Generation Parameter STACKSIZE needed to be
increased. CA recommended a value of 3000, our initial value was 1024,
apparently 1024 was not enough to allow for startup. Once the sysgen change was made
and the stack size increased the system started with no problems.

This issue was not documented in the cover letter that came with the
installation tape.

I would recommend that you change this value in all your current systems
that you are planning to convert to IDMS 16.0 SP2 to avoid this issue.

Bill Allen
ARCH Consulting Associates, Ltd.

"
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 release 16.0 Installation issue
"See GI76847 recommendation for STACKSIZE in SYSGEN is 3000.

Edward A. Timm
Sallie Mae, Senior Database Analyst
ETIMM@salliemae.com
(317) 596-1182
Fax (317) 595-1494
ARCHCONB@aol.com 10/10/2005 12:13:47 PM >>>
Hello Everyone:

This is meant as a heads up to everyone in the process of installing
IDMS
Release 16.0 SP2.

We received a 3964 during startup. In contacting CA for support on
Saturday
it was learned that the System Generation Parameter STACKSIZE needed to
be
increased. CA recommended a value of 3000, our initial value was 1024,
apparently 1024 was not enough to allow for startup. Once the sysgen
change was made
and the stack size increased the system started with no problems.

This issue was not documented in the cover letter that came with the
installation tape.

I would recommend that you change this value in all your current
systems
that you are planning to convert to IDMS 16.0 SP2 to avoid this issue.

Bill Allen
ARCH Consulting Associates, Ltd.

This E-Mail has been scanned for viruses.

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








Normal

Normal
Re: Verifying an IDMS Install
"Joe -

I used to think that casual testing in a test or sandbox environment for a
period of 3 to 6 months was all that was needed.
I no longer believe that.

If your IDMS regions are large in terms of transaction volumes and in the
number of applications they run, then
the best plans I have seen are those that exercise every online and batch
component in your test environments prior to moving to production.
The testing is done using scripts prepared by each functional applications
development department.

This level of testing is especially necessary if you're running a lot of
assembler custom-code or have applications using SNA.

You don't necessarily have to get end-users get involved as long as your
development staff knows the applications inside and out.

Whatever test plan you used for Y2K is the level of effort you should go
through with a new release of IDMS software.

We found a handful of issues this way with 16.0 - SP2 and were glad we went
through this kind of effort.
Also, you have the comfort level and confidence that all bases were covered
when it comes time to switch on production.

A backout plan is always a requirement, but we had a lot riding on getting
the release in on our scheduled date.
A backout was only going to be a desparate last resort.

Thanks.
Jon Gocher


----- Original Message -----
From: ""Lupico, Joe"" <Joe.Lupico@AIG.COM>
To: <IDMS-L@LISTSERV.IUASSN.COM>
Sent: Monday, October 10, 2005 11:26 AM
Subject: Verifying an IDMS Install

Hi All,
Management here is once again on a mission to have documentation produced
on how a product is verified once it's installed.
I would like to query the list to find out how you (if you are the
installer) verifies that IDMS has been installed correctly and ALL the
components are working.
In my case, I have to install every IDMS product - both base and tool. I
have no way, that I know of, that I could possibly test that every
component
is working, especially when I'm in an environment where not all products
are
utilized by clients. There are a lot of products within the IDMS family
that I I don't know how to use, or can not test because I simply don't
have
the resources (database and/or application). This is especially true
since
I initially install products into an LPAR that is only used by system
programmers.
I have always installed IDMS and tested that regions come up with no
problems, CICS/TSO/VTAM interfaces are working, and the basic compilers
work
- IDD, SSC, etc. Beyond that, I install into test regions with a quick
backout plan readily available. It's worked for me for over 15 years.

Joe Lupico
IDMS System Support
""Our World is a Happy World""

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








Normal

Normal
Re: Verifying an IDMS Install
"Jon,
Thanks for the reply. However, this assumes that you have the help/aid of
others in testing the software, and can do that testing in a test
environment. What would you do if you had to verify the software was good
BEFORE putting it in test and allowing access to the development community?
That's the question I will be asked - How do I (as the installer, absent
of any other help) verify an install?

Joe Lupico
IDMS System Support
""Our World is a Happy World""

Outcomes