ca.portal.admin

Re: S0F8 with Date Simulator & ZIIP : R17 0F8 zIIP date

Discussion created by ca.portal.admin on Mar 3, 2010
S0F8-4 problem with ZIIP=3DY explanation.
Date Simulator products require PTF RI05855 to be applied to the RHDCOMVS
module and to the startup module if you do not use RHDCOMVS in your startu=
p.
This PTF was created for Date Simulator products which require that all
STORE CLOCK instructions issue an SVC that calls the DATE SIMULATOR produc=
t.
*
If you are using zIIP processing, our code offloads work to zIIP processor=
s.
When running with ZIIP=3DY, you are actually running under an SRB and not =
under
a TCB.
It is ILLEGAL to issue an SVC if you are not running in TCB mode.
Here is a description of S0F8 Reason Code 4.
S0F8 -
Explanation: The issuer of a Supervisor Call (SVC) instruction was not i=
n
the correct mode to issue the SVC. A hexadecimal reason code in the
RTM2CRC field of the RTM2WA data area explains the error:
=20
Code Explanation
=20
04 The issuer was in a mode other than task control block (TCB)
mode.
*
Since Date Simulator products require that our STCK instructions be zapped
with an SVC call, you can NOT run ZIIP=3DY on a CA IDMS CV that is using
Date Simulator products.
You will always get S0F8 abends when you have the SVC zap replacing the
STCK (STORE CLOCK) instructions and ZIIP=3DY on the startup parm.
*
CA IDMS CVs that use Date Simulator products must run with ZIIP=3DN.

Edward F McKinney
CA=20
Senior Sustaining Engineer
CA-IDMS
Tel: +1-508-628-8171
Fax: +1-508-628-8715
Edward.McKinney@ca.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: S0F8 with Date Simulator & ZIIP : R17 0F8 zIIP date
"FYI: This restriction does not apply to the HSL Date Simulator, which also does not need PTF RI05855. We are using this product with ""ZIIP=Y"".

Outcomes