ca.portal.admin

Re:Re: [IDMSVENDOR-L] r15.0 to r16.0 migration

Discussion created by ca.portal.admin on May 15, 2008
Chris,

Check QI82743 before you go to z/os v 1.9. z/os v 1.9 changes the
AllowUserKeyCSA default to 'no' where it used to be 'yes'. We were lucky
and kept this parameter at 'yes' since there was other applications that
required it and so we did not have to do anything for IDMS. We have been
running z/os 1.9 in Production since May 4.

Petra


Chris Hoelscher wrote:
we are on 1.8 - soon to be 1.9


i just downloaded R16 0710 (SP6?)




What version of the z/OS are you on Chris? You must be looking at 16.0
post sp2?

n.


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: r15.0 to r16.0 migration
"Jim,

The default is NO, but we are running z/OS 1.9 with YES (which used to
be the default) as we have with z/OS 1.7.

Mary Sciuto
Tufts University

Jim Criscuolo wrote:
Hello All,

We are currently running IDMS under z/OS 1.9 with allowuserkeycsa=YES
and I know IBM recommends NO. Are there many other shops running with
YES for this parameter or did most of you follow the instructions in
QI82743?

We are trying to determine a path forward regarding this issue.

TIA,

Jim

-----Original Message-----
From: IDMS Public Discussion Forum [mailTo:IDMS-L@LISTSERV.IUASSN.COM]
On Behalf Of Petra LaFrese
Sent: Thursday, May 15, 2008 5:00 PM
To: IDMS-L@LISTSERV.IUASSN.COM
Subject: Re: [IDMSVENDOR-L] r15.0 to r16.0 migration

Chris,

Check QI82743 before you go to z/os v 1.9. z/os v 1.9 changes the
AllowUserKeyCSA default to 'no' where it used to be 'yes'. We were lucky
and kept this parameter at 'yes' since there was other applications that
required it and so we did not have to do anything for IDMS. We have been
running z/os 1.9 in Production since May 4.

Petra


Chris Hoelscher wrote:
we are on 1.8 - soon to be 1.9


i just downloaded R16 0710 (SP6?)




What version of the z/OS are you on Chris? You must be looking at 16.0
post sp2?

n.


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] r15.0 to r16.0 migration
"Jim,

The default is NO, but we are running z/OS 1.9 with YES (which used to
be the default) as we have with z/OS 1.7.

Mary Sciuto
Tufts University

Jim Criscuolo wrote:
Hello All,

We are currently running IDMS under z/OS 1.9 with allowuserkeycsa=YES
and I know IBM recommends NO. Are there many other shops running with
YES for this parameter or did most of you follow the instructions in
QI82743?

We are trying to determine a path forward regarding this issue.

TIA,

Jim

-----Original Message-----
From: IDMS Public Discussion Forum [mailTo:IDMS-L@LISTSERV.IUASSN.COM]
On Behalf Of Petra LaFrese
Sent: Thursday, May 15, 2008 5:00 PM
To: IDMS-L@LISTSERV.IUASSN.COM
Subject: Re: [IDMSVENDOR-L] r15.0 to r16.0 migration

Chris,

Check QI82743 before you go to z/os v 1.9. z/os v 1.9 changes the
AllowUserKeyCSA default to 'no' where it used to be 'yes'. We were lucky
and kept this parameter at 'yes' since there was other applications that
required it and so we did not have to do anything for IDMS. We have been
running z/os 1.9 in Production since May 4.

Petra


Chris Hoelscher wrote:
we are on 1.8 - soon to be 1.9


i just downloaded R16 0710 (SP6?)




What version of the z/OS are you on Chris? You must be looking at 16.0
post sp2?

n.


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: r15.0 to r16.0 migration
"Hi Jim,

We are running with the allowuserkeycsa=yes parameter. It turned out our
scheduling software (Jobmaster) needed the parameter to be yes. So we
didn't have to do anything. The Systems group just must remember to keep
it that way for any future upgrades.

Hope this helps,
Petra

JCriscuolo@us.imshealth.com wrote:
Hello All,

We are currently running IDMS under z/OS 1.9 with allowuserkeycsa=YES
and I know IBM recommends NO. Are there many other shops running with
YES for this parameter or did most of you follow the instructions in
QI82743?

We are trying to determine a path forward regarding this issue.

TIA,

Jim

-----Original Message-----
From: IDMS Public Discussion Forum [mailTo:IDMS-L@LISTSERV.IUASSN.COM]
On Behalf Of Petra LaFrese
Sent: Thursday, May 15, 2008 5:00 PM
To: IDMS-L@LISTSERV.IUASSN.COM
Subject: Re: [IDMSVENDOR-L] r15.0 to r16.0 migration

Chris,

Check QI82743 before you go to z/os v 1.9. z/os v 1.9 changes the
AllowUserKeyCSA default to 'no' where it used to be 'yes'. We were lucky
and kept this parameter at 'yes' since there was other applications that
required it and so we did not have to do anything for IDMS. We have been
running z/os 1.9 in Production since May 4.

Petra


Chris Hoelscher wrote:
we are on 1.8 - soon to be 1.9


i just downloaded R16 0710 (SP6?)




What version of the z/OS are you on Chris? You must be looking at 16.0
post sp2?

n.


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] r15.0 to r16.0 migration
"Hi Jim,

We are running with the allowuserkeycsa=yes parameter. It turned out our
scheduling software (Jobmaster) needed the parameter to be yes. So we
didn't have to do anything. The Systems group just must remember to keep
it that way for any future upgrades.

Hope this helps,
Petra

JCriscuolo@us.imshealth.com wrote:
Hello All,

We are currently running IDMS under z/OS 1.9 with allowuserkeycsa=YES
and I know IBM recommends NO. Are there many other shops running with
YES for this parameter or did most of you follow the instructions in
QI82743?

We are trying to determine a path forward regarding this issue.

TIA,

Jim

-----Original Message-----
From: IDMS Public Discussion Forum [mailTo:IDMS-L@LISTSERV.IUASSN.COM]
On Behalf Of Petra LaFrese
Sent: Thursday, May 15, 2008 5:00 PM
To: IDMS-L@LISTSERV.IUASSN.COM
Subject: Re: [IDMSVENDOR-L] r15.0 to r16.0 migration

Chris,

Check QI82743 before you go to z/os v 1.9. z/os v 1.9 changes the
AllowUserKeyCSA default to 'no' where it used to be 'yes'. We were lucky
and kept this parameter at 'yes' since there was other applications that
required it and so we did not have to do anything for IDMS. We have been
running z/os 1.9 in Production since May 4.

Petra


Chris Hoelscher wrote:
we are on 1.8 - soon to be 1.9


i just downloaded R16 0710 (SP6?)




What version of the z/OS are you on Chris? You must be looking at 16.0
post sp2?

n.


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
Any experience with file cache in memory under z\VSE
"Dear Friends,=20

=20

I am currently running IDMS R16 0710 under z\VSE 4.11

=20

Does anyone have any experiences using file cache in memory in this
environment?=20

=20

Nigel Salway

Senior Analyst

1900 Albert Street

Regina, SK S4P 4K8

Telephone: (306) 761-4063 =20

Fax: (306) 761-4141 =20

=20

CONFIDENTIALITY NOTICE: Proprietary/Confidential Information belonging
to CGI Group Inc. and its affiliates may be contained in this message.
If you are not a recipient indicated or intended in this message (or
responsible for delivery of this message to such person), or you think
for any reason that this message may have been addressed to you in
error, you may not use or copy or deliver this message to anyone else.
In such case, you should destroy this message and are asked to notify
the sender by reply email.

=20
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Any experience with file cache in memory under z\VSE
"Dear Friends,



I am currently running IDMS R16 0710 under z\VSE 4.11



Does anyone have any experiences using file cache in memory in this
environment?



Nigel Salway

Senior Analyst

1900 Albert Street

Regina, SK S4P 4K8

Telephone: (306) 761-4063

Fax: (306) 761-4141



CONFIDENTIALITY NOTICE: Proprietary/Confidential Information belonging
to CGI Group Inc. and its affiliates may be contained in this message.
If you are not a recipient indicated or intended in this message (or
responsible for delivery of this message to such person), or you think
for any reason that this message may have been addressed to you in
error, you may not use or copy or deliver this message to anyone else.
In such case, you should destroy this message and are asked to notify
the sender by reply email.


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








Normal

Normal
Re: Batch UCF Jobs
"Very simple - just use the same job name for each of them. MVS will
enqueue on jobname. If that is not possible, use the a file name with
DISP=OLD like someone else said.

Dan Miley
Lockheed Martin

Outcomes