ca.portal.admin

Question about CA - HYPER NOTIFICATION - RO20143 IDMS - OS getmain problem

Discussion created by ca.portal.admin on Jul 27, 2010
This refers to IBM apar OA27291 on z/OS 1.10. If we are going to 1.11 does anyone know if we still need to apply it?

Hoping support will see this.

TIA


Jim


Jim Rice
jlrice@southernco.com
ph (404) 506-4148
Fax (404) 506- 4870
Customer Focused/Client Oriented since 1991

This e-mail and any of its attachments may contain proprietary Southern Company and/or affiliate information that is privileged, confidential, or protected by copyright belonging to Southern Company and/or its affiliates. This e-mail is intended solely for the use of the individual or entity for which it is intended. If you are not the intended recipient of this e-mail, any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this e-mail is contrary to the rights of Southern Company and/or its affiliates and is prohibited. If you are not the intended recipient of this e-mail, please notify the sender immediately by return e-mail and permanently delete the original and any copy or printout of this e-mail and any attachments. Thank you.
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
PU or EU in SQL?
"Does anybody know if it is possible to run an SQL update using IDMSBCF =
against a network DB in Protected or Exclusive Update?
=20
For example if I want to do DELETE FROM PSCHEMA.CUSTOMER; then the =
number of record locks generated is enormous and I want at least PU or =
even better EU anyway because clearly I don't want anybody trying to add =
or modify a record when I am deleting the whole lot. My system would =
generate several hundred million locks and go SOS if I tried it in SU. =
But my journals are big enough to do it.=20
=20
At present I have to find a field which I can select on to break up the =
deletes into manageable chunks and then I can issue a Commit in between. =
But that doesn't solve the sharing the DB problem.
=20
Example:
=20
DELETE FROM PSCHEMA.CUSTOMER WHERE CUST_NO < 10000;
COMMIT;
DELETE FROM PSCHEMA.CUSTOMER WHERE CUST_NO < 20000;
COMMIT;
etc etc until all the CUSTOMER records have gone away.
=20
Actually it is more likely that I would be doing an Update and not a =
Delete but the principle is the same. =20
=20
As far as I can see, you always get Shared Update when you use an SQL. =
Obviously I should and do use DML to do such things but my question is =
still valid.
=20
Before anybody tells me to use FORMAT on the AREA, I would point out =
that the area can and does contain other record types. And anyway this =
is a mythical example. I need the Customers otherwise I don't get paid.=20
=20
And I don't want to run it local either. =20
=20
______________________________________________________________
=20
Chris Trayler, IXD
Bank Julius Baer & Co. Ltd.
P. O. Box, CH-8010 Z=FCrich, Switzerland
Telephone +41 (0)58 887 4332, Fax +41 (0)58 887 4969
www.juliusbaer.com <http://www.juliusbaer.com/>=20
=20
______________________________________________________________
*****JuliusBaer Disclaimer***** This e-mail is for the intended =
recipient only and may contain confidential or privileged information. =
If you have received this e-mail by mistake, please contact us =
immediately and completely delete it (and any attachments) and do not =
forward it or inform any other person of its contents. If you send us =
messages by e-mail, we take this as your authorization to correspond =
with you by e-mail, however, we will not accept the electronic =
transmission of orders/instructions without a specific agreement being =
in place to govern the same. If you do not wish to receive any further =
e-mail correspondence please let us know. E-mail transmission cannot be =
guaranteed to be secure or error-free as information could be =
intercepted, amended, corrupted, lost, destroyed, arrive late or =
incomplete, or contain viruses. Neither the Julius Baer Group nor the =
sender accept liability for any errors or omissions in the content of =
this message which arise as a result of its e-mail transmission. Please =
note that all e-mail communications to and from the Julius Baer Group =
may be monitored. This communication is for informational purposes only. =
It is not intended as an offer or solicitation for the purchase or sale =
of any financial instrument or as an official confirmation of any =
transaction.
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
PU or EU in SQL?
"Does anybody know if it is possible to run an SQL update using IDMSBCF against a network DB in Protected or Exclusive Update?

For example if I want to do DELETE FROM PSCHEMA.CUSTOMER; then the number of record locks generated is enormous and I want at least PU or even better EU anyway because clearly I don't want anybody trying to add or modify a record when I am deleting the whole lot. My system would generate several hundred million locks and go SOS if I tried it in SU. But my journals are big enough to do it.

At present I have to find a field which I can select on to break up the deletes into manageable chunks and then I can issue a Commit in between. But that doesn't solve the sharing the DB problem.

Example:

DELETE FROM PSCHEMA.CUSTOMER WHERE CUST_NO < 10000;
COMMIT;
DELETE FROM PSCHEMA.CUSTOMER WHERE CUST_NO < 20000;
COMMIT;
etc etc until all the CUSTOMER records have gone away.

Actually it is more likely that I would be doing an Update and not a Delete but the principle is the same.

As far as I can see, you always get Shared Update when you use an SQL. Obviously I should and do use DML to do such things but my question is still valid.

Before anybody tells me to use FORMAT on the AREA, I would point out that the area can and does contain other record types. And anyway this is a mythical example. I need the Customers otherwise I don't get paid.

And I don't want to run it local either.

______________________________________________________________

Chris Trayler, IXD
Bank Julius Baer & Co. Ltd.
P. O. Box, CH-8010 Zürich, Switzerland
Telephone +41 (0)58 887 4332, Fax +41 (0)58 887 4969
www.juliusbaer.com <http://www.juliusbaer.com/>

______________________________________________________________
*****JuliusBaer Disclaimer***** This e-mail is for the intended recipient only and may contain confidential or privileged information. If you have received this e-mail by mistake, please contact us immediately and completely delete it (and any attachments) and do not forward it or inform any other person of its contents. If you send us messages by e-mail, we take this as your authorization to correspond with you by e-mail, however, we will not accept the electronic transmission of orders/instructions without a specific agreement being in place to govern the same. If you do not wish to receive any further e-mail correspondence please let us know. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, amended, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Neither the Julius Baer Group nor the sender accept liability for any errors or omissions in the content of this message which arise as a result of its e-mail transmission. Please note that all e-mail communications to and from the Julius Baer Group may be monitored. This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction.
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Is anyone else having trouble accessing the IDMS-L archives?
"Both of Steve's suggestions worked. Thanks!

Outcomes