ca.portal.admin

Re:Re: [IDMSVENDOR-L] batch JCL FTP changes to support.ca.com

Discussion created by ca.portal.admin on Dec 2, 2009
Answering one's post is only a sign of insanity if it is repeated and you
get into a heated argument with yourself. Insanity becomes clear when you
lose the argument.

John

--- On Wed, 12/2/09, Chris Hoelscher <chrishoelscher@INSIGHTBB.COM> wrote:
From: Chris Hoelscher <chrishoelscher@INSIGHTBB.COM>
Subject: Re: [IDMSVENDOR-L] batch JCL FTP changes to support.ca.com
To: IDMS-L@LISTSERV.IUASSN.COM
Date: Wednesday, December 2, 2009, 1:07 PM
Chris Hoelscher wrote:
i will see if i can find the actual doc - if you go to
the support,.ca.com
front page - there may be a bullet about secure FTP
there that might have
instructions

look at

https://support.ca.com/irj/portal/anonymous/phpdocs?filePath=0/common/sftshe
lpfile.html
>
it also appears that the old way MIGHT work if your
corporate firewall
does not block ip addresses: see

https://support.ca.com/irj/portal/anonymous/phpdocs?filePath=0/common/custom
ernotice.html#sftsfix
>
all i can tell ya is - the old ftp quit working for me - i
needed to
switch to the new one (could be perhaps because of the fix
mentioned in
the second link)

ps - is answering ones one post a sign of insanity?
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
R17 upgrade tip for CICS
"Do not try to mix IDMS releases in a CICS region. This has sometimes worke=
d in the past, but not this time.

When we upgraded a CV and its CICS region from R16 to R17, the dedicated ta=
sk and UCF connections worked, but all of the CICS/IDMS programs started ab=
ending. The symptoms were D002 in RHDCWTL, storage violations, and DYLD in=
RHDCLODR.

This CICS region had connections to two other CV's, both of which are still=
at R16. Although these connections are no longer used, their IDMSINTC pro=
grams (R16 versions) were still being executed at CICS startup. Removing t=
hese programs from the CICS PLT resolved the problem.

Kay Rozeboom
State of Iowa
Information Technology Enterprise
Department of Administrative Services
Telephone: 515.281.6139 Fax: 515.281.6137
Email: Kay.Rozeboom@Iowa.Gov
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
R17 upgrade tip for CICS
"Do not try to mix IDMS releases in a CICS region. This has sometimes worked in the past, but not this time.

When we upgraded a CV and its CICS region from R16 to R17, the dedicated task and UCF connections worked, but all of the CICS/IDMS programs started abending. The symptoms were D002 in RHDCWTL, storage violations, and DYLD in RHDCLODR.

This CICS region had connections to two other CV's, both of which are still at R16. Although these connections are no longer used, their IDMSINTC programs (R16 versions) were still being executed at CICS startup. Removing these programs from the CICS PLT resolved the problem.

Kay Rozeboom
State of Iowa
Information Technology Enterprise
Department of Administrative Services
Telephone: 515.281.6139 Fax: 515.281.6137
Email: Kay.Rozeboom@Iowa.Gov
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: R17 upgrade tip for CICS
"I'd like to add a point of clarification to Kay's note. =20

Within a given CICS region, all your IDMSINTC interfaces and your
""mini-CV"" IDMS modules must all be from the same release of IDMS.
Problems will arise if you start an IDMSINTC interface compiled for one
release and try to run it with an IDMS run-time library from another
release. Only one IDMS run-time ""mini-CV"" can be loaded into a given
CICS region. =20

On the other hand, as long as the IDMSINTC interfaces are from the same
release, they should be able to access IDMS back-end CVs at different
releases. =20
For example,
Compile CICSOPT with CWADISP=3D4,SYSCTL=3DSYSCTL04 using R17.0 =
compile/link
libraries.
Resulting load module is INTC04.
Compile CICSOPT with CWADISP=3D8,SYSCTL=3DSYSCTL08 using R17.0 =
compile/link
libraries.
Resulting load module is INTC08.=20
Bring up CICS region with DFHRPL pointing to a R17.0 IDMS library.
Start both INTC interfaces.
Bring up CV04 under R16.0 with SYSCTL where DSN matches CICS SYSCTL04.
Bring up CV08 under R17.0 with SYSCTL where DSN matches CICS SYSCTL08.

Now applications using CWADISP=3D4 should be able to successfully access
CV04 at R16.0 while applications using CWADISP=3D8 should be able to
successfully access CV08 at R17.0.

Mike Mickelsen
CA IDMS Level 2 support

Outcomes