ca.portal.admin

Re: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=Y 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
startup.
This PTF was created for Date Simulator products which require that all
STORE CLOCK instructions issue an SVC that calls the DATE SIMULATOR
product.
*
If you are using zIIP processing, our code offloads work to zIIP
processors.
When running with ZIIP=Y, 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 in
the correct mode to issue the SVC. A hexadecimal reason code in the
RTM2CRC field of the RTM2WA data area explains the error:

Code Explanation

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=Y 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=Y on the startup parm.
*
CA IDMS CVs that use Date Simulator products must run with ZIIP=N.

Edward F McKinney
CA
Senior Sustaining Engineer
CA-IDMS
Tel: +1-508-628-8171
Fax: +1-508-628-8715
Edward.McKinney@ca.com
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
IDMS Connections March 2010 Issue now available at IUASSN.ORG
"Members of the IUA may now download the March 2010 ""IDMS Connections"" from http://iuassn.org --> Archives --> Connections! If the list of available issues does not allow you to download, then you have not signed in to the site - you will need to become a member - this is free - just follow the ""Join the IUA!"" link in the top left corner of the home page!

The Table of Contents is provided here to pique your interest. Note that, with daylight saving changes rapidly approaching, there is an article on Page 11 which may be useful to those who have yet to decide on their operational procedures for their IDMS-DB/DC regions:

Message from the International Chair ...3
Interview with Art Cartier ...3
Business Value Corner ...5
Health Checks for Release 17 ...6
Health Checks Stop Press ...9
Tips for WI-FI Security on the Road ...11
Daylight Savings Time ...11
CA-IDMS and Artificial Intelligence ...12
Humour in Inbox ...13
Calling a Date a Date ...14
SQL Update Statistics ...16
Mixed Page Group Implementation ...21
CA World Planning ...23
IDMS-L Rules ...26

The following attributions were omitted - my apologies to the authors/contributors - but also my thanks for sending in your material which we try to treat with due respect.

""Calling a Date a Date"" was contributed by
Ian Hill
CA
Hill, Ian [Ian.Hill@ca.com]

""SQL Update Statistics"" was contributed by:
David E Matthews
LOGIS DBA
david.matthews@dhl.com

I hope that you enjoy this issue - and that you will pass on hard and/or soft copy of this issue to your fellow work mates - take care - cheers - Gary

Gary Cherlet
Justice Technology Services
Department of Justice, SA Government
Editor ""IDMS Connections""
IUA International Board Member
President Australian IDMS User Group (OZIUA)

"""""""" Telephone +61 (0)8 8226 5199
@@ Facsimile +61 (0)8 8226 5311
> Mobile +61 (0)41 333 1613
\/ MailTo:gary.cherlet@sa.gov.au

This e-mail message and any attachments are qualified as follows: Addressing: If you have received this e-mail in error, please advise by reply e-mail to the sender. Please also destroy the original transmission and its contents. Confidentiality: This e-mail may contain confidential information which also may be legally privileged. Only the intended recipient(s) may access, use, distribute or copy this e-mail. Individual Views: Unless otherwise indicated, the views expressed are those of the sender, not Justice Technology Services. Computer Viruses: It is the recipient's responsibility to check the e-mail and any attached files 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
IDMS Connections March 2010 Issue now available at IUASSN.ORG
"Members of the IUA may now download the March 2010 ""IDMS Connections"" from =
http://iuassn.org --> Archives --> Connections! If the list of available is=
sues does not allow you to download, then you have not signed in to the sit=
e - you will need to become a member - this is free - just follow the ""Join=
the IUA!"" link in the top left corner of the home page!

The Table of Contents is provided here to pique your interest. Note that, w=
ith daylight saving changes rapidly approaching, there is an article on Pag=
e 11 which may be useful to those who have yet to decide on their operation=
al procedures for their IDMS-DB/DC regions:

Message from the International Chair ...3
Interview with Art Cartier ...3
Business Value Corner ...5
Health Checks for Release 17 ...6
Health Checks Stop Press ...9
Tips for WI-FI Security on the Road ...11
Daylight Savings Time ...11
CA-IDMS and Artificial Intelligence ...12
Humour in Inbox ...13
Calling a Date a Date ...14
SQL Update Statistics ...16
Mixed Page Group Implementation ...21
CA World Planning ...23
IDMS-L Rules ...26

The following attributions were omitted - my apologies to the authors/contr=
ibutors - but also my thanks for sending in your material which we try to t=
reat with due respect.

""Calling a Date a Date"" was contributed by
Ian Hill
CA=20
Hill, Ian [Ian.Hill@ca.com]

""SQL Update Statistics"" was contributed by:
David E Matthews
LOGIS DBA
david.matthews@dhl.com

I hope that you enjoy this issue - and that you will pass on hard and/or so=
ft copy of this issue to your fellow work mates - take care - cheers - Gary=
=20

Gary Cherlet
Justice Technology Services
Department of Justice, SA Government
Editor ""IDMS Connections""
IUA International Board Member
President Australian IDMS User Group (OZIUA)

"""""""" Telephone +61 (0)8 8226 5199
@@ Facsimile +61 (0)8 8226 5311
> Mobile +61 (0)41 333 1613
\/ MailTo:gary.cherlet@sa.gov.au

This e-mail message and any attachments are qualified as follows: Addressin=
g: If you have received this e-mail in error, please advise by reply e-mai=
l to the sender. Please also destroy the original transmission and its con=
tents. Confidentiality: This e-mail may contain confidential information w=
hich also may be legally privileged. Only the intended recipient(s) may ac=
cess, use, distribute or copy this e-mail. Individual Views: Unless otherw=
ise indicated, the views expressed are those of the sender, not Justice Tec=
hnology Services. Computer Viruses: It is the recipient's responsibility t=
o check the e-mail and any attached files for viruses.
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
WTOREXIT under 17.0
"Has anyone had any issues with the WTOREXIT under 17.0? Prior to 17, I
would link the WTOEXIT and WTOREXIT into the startup module. While it
appears that you can still do that under 17, you loose the ability to run on
a zIIP if you do so. I tried linking a single WTOEXIT module and telling
the startup to use it for WTOEXIT and WTOREXIT. WTOR failed to work
correctly. By creating two modules, I got the WTOR to work (sort of). My
system hangs at shutdown with DB-SYNCHRO from Cogito when WTOREXIT is
loaded. If I run without WTOREXIT, no hang at shutdown. I put the WTOREXIT
in the startup, no hang at shutdown.



Any ideas would be appreciated.



Mark Grindstaff

mgrindstaff@prodigy.net
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
WTOREXIT under 17.0
"Has anyone had any issues with the WTOREXIT under 17.0? Prior to 17, I
would link the WTOEXIT and WTOREXIT into the startup module. While it
appears that you can still do that under 17, you loose the ability to run on
a zIIP if you do so. I tried linking a single WTOEXIT module and telling
the startup to use it for WTOEXIT and WTOREXIT. WTOR failed to work
correctly. By creating two modules, I got the WTOR to work (sort of). My
system hangs at shutdown with DB-SYNCHRO from Cogito when WTOREXIT is
loaded. If I run without WTOREXIT, no hang at shutdown. I put the WTOREXIT
in the startup, no hang at shutdown.



Any ideas would be appreciated.



Mark Grindstaff

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








Normal

Normal
Re: WTOREXIT under 17.0
"if you run WITHOUT DB-Syncro (from Cogito) does the wtor and wto exits
work as designed without hang?

i link my WTOEXIT thru SMP/E and start up as follows:

//IDMP75DB EXEC PGM=IDMSDC,REGION=2047M,
// PARM=('S=075','DMCL=DMPCV75','FSTG=4000','MT=Y','MTQD=3'
// 'SVC=250','WTO=WTOEXIT','ZIIP=Y','AUTOTASKS=Y',
// 'SUBT=6')




Chris Hoelscher
IDMS/DB2 Database Architect
Humana Inc
502-476-2538
choelscher@humana.com

you only need to test the programs that you want to work correctly



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 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: [IDMSVENDOR-L] WTOREXIT under 17.0
"if you run WITHOUT DB-Syncro (from Cogito) does the wtor and wto exits
work as designed without hang?

i link my WTOEXIT thru SMP/E and start up as follows:

//IDMP75DB EXEC PGM=IDMSDC,REGION=2047M,
// PARM=('S=075','DMCL=DMPCV75','FSTG=4000','MT=Y','MTQD=3'
// 'SVC=250','WTO=WTOEXIT','ZIIP=Y','AUTOTASKS=Y',
// 'SUBT=6')




Chris Hoelscher
IDMS/DB2 Database Architect
Humana Inc
502-476-2538
choelscher@humana.com

you only need to test the programs that you want to work correctly



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
Re: [IDMSVENDOR-L] WTOREXIT under 17.0
"My parm list is similar

//DLP1CV EXEC PGM=IDMSDC,REGION=0M,TIME=1440,
// PARM=('S=80',
// 'MT=N',
// 'WTOEXIT=WTOEXIT',
// 'WTOREXIT=WTOREXIT',
// 'DMCL=DLP1DMCL')

Everything works with this configuration WITHOUT DB-SYNCHRO.

With this configuration and DB-SYNCHRO active the CV hangs. A series of
SYNCHRO messages appear

DB905004
DB905005
DB905008
DB905006

Then they repeat until I cancel the region.

When I run the ""old"" way (WTO/WTOR linked with the startup everything works
like it is supposed to.

Messages 4 and 5 are Synchro messages. 8 and 6 are for DB-SHARE. We don't
use the SHARE component in this environment. I'm going to try to deactivate
it and see what happens.

What my gut is telling me is that I might have an affinity problem. There
is a recently published APAR for the WTOEXIT that talks about this. We
found this while testing multitasking under 16.0. We started getting ACF2
violations from the journal submit when MT was turned on. The 16.0 version
takes about the problem extending beyond ACF2. I see that the same fix was
published for 17. I pulled the 17.0 version yesterday, but haven't
installed it yet. It's on the list of things to do today.

Mark Grindstaff

Outcomes