ca.portal.admin

Re:R17 upgrade - SVC problem

Discussion created by ca.portal.admin on May 4, 2009
When our MVS systems programmer implemented the new SVC for R17 this weekend
with an IPL, it broke the old SVC currently in use by all of our R16 CV's.
They all abended at startup with ""SEF3"" (SVC 243, which is the R16 SVC). We
backed out the new SVC, then the old one worked OK.

Any ideas about what we might have done wrong?

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
Re: R17 upgrade - SVC problem
"If you reload (CAIRIM) a new SVC into your CPU and CA-IDMS Cvs are
running on that CPU with that same SVC number, those CVs that are up
will not abend with an SEnn abend but no EXTERNAL jobs that use EREs
will communicate with the CVs that were up until they are recycled
because the EREs in MVS CSA storage will be reinitialized for that SVC
when you CAIRIM in the same SVC number. FYI.
Ed

Outcomes