ca.portal.admin

R17 upgrade - SVC problem

Discussion created by ca.portal.admin on May 4, 2009
Latest reply on May 4, 2009 by ca.portal.admin
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 Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
FW: R17 upgrade - SVC problem
"We think we have resolved the problem with help from Brian Brendlinger of C=
A. (Won't know for sure until we IPL on Sunday morning.)

Prior to R15, CAIRIM automatically loaded a security module called CAS9SEC.=
Now you have to load it yourself with the CAIRIM syntax below, which we w=
ere not doing. Although we have been on R16 for several years, we did not =
get caught by this until now because CAIRIM was still loading the old R14 S=
VC, which in turn loaded CAS9SEC. When our MVS person added the syntax to =
load the R17 SVC, he removed the old R14 syntax. So CAS9SEC did not get lo=
aded.=20

PRODUCT(CA-SECURITY/INIT) VERSION(S910) INIT(S910INIT)

Outcomes