ca.portal.admin

Re:PU or EU in SQL?

Discussion created by ca.portal.admin on Jul 28, 2010
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: DYNAM vs NODYNAM
"See also Section 6.4 DEFAULT PROGRAM Statement- my expectation is that NULL=
PDE's created dynamically for anything lloaded from the dictionary load ar=
ea (which has not been previously defined to sysgen) will gain the DEFAULT =
PROGRAM attributes that have been set as PERMANENT.

DYNAMIC/NODYNAMIC is often misunderstood - what it is used for is to ensure=
that a predefined program with NODYNAM specified can not be replaced by an=
other version of the program being found higher up in the LOADLIST. Here's =
a scenario worth considering:
1) LOADLIST has Dictionaries APPLOAD SYSLOAD then LOADLIB
2) DIALOG1 is predefined with DYNAM and as being loaded from a LOADLIB
3) Somebody uses DIALOG1 and it gets loaded from LOADLIB - however the syst=
em has searched APPLOAD and SYSLOAD to see if DIALOG1 lives there - not fin=
ding it there it goes to LOADLIB
4) Developer / migratory / whoever compiles DIALOG1 in APPLOAD load area
5) Next use of DIALOG1 the system searches the LOADLIST and finds DIALOG1 i=
n APPLOAD - so that is the version that gets loaded and executed - from tha=
t point on the APPLOAD version of DIALOG1 will be used

If you want to ensure that the only version of DIALOG1 that gets used at ru=
n time is from LOADLIB - then specify NODYNAM. This is both a security issu=
e, to ensure that you only ever get the one version of a dialog, and a perf=
ormance issue as by specifying NODYNAM you reduce the searches that must be=
performed to locate the program - even though it has already been loaded!=
=20

You of course could define DIALOG1 to SYSGEN and specify DICTNAME APPLOAD N=
ODYNAM - which means that you have a reduced search path and that you will =
only ever run the version that comes from APPLOAD.

At least that is how I understand it. If programs that occupy NULL PDE's in=
one CV show up with DYNAM and in other CV's with NODYNAM then I would look=
at the DEFAULT PROGRAM setting.

Also worth noting that some users might have one LOADLIST and other users a=
different LOADLIST - which can be set by DCUF if allowed or through User P=
rofile (in which case the LOADLIST may be either fixed or able to be change=
d OVERRIDE YES/NO).

HTH - and looking forward to corrections if I have said anything contrary t=
o the way ""loader"" works - cheers - Gary=20

SYSGEN 17.0 NO ERRORS DICT=3DSYSDICT
DIS SYS 10 WITH NONE. =20
*+   ADD SYSTEM 10                                          =20
*+       SYSTEM ID IS SYST0010                              =20
*+       .                                                  =20
DIS ALL DEFAULT PERM PROG. =20
*+   ADD DEFAULT PERMANENT PROGRAM                          =20
*+       DATE CREATED IS      12/13/90                      =20
*+       DATE LAST UPDATED IS 03/11/91                      =20
*+       PREPARED BY JDAINB                                 =20
*+       REVISED  BY JDAINB                                 =20
*+       CONCURRENT                                         =20
*+       NODYNAMIC                                          =20
*+       DUMP THRESHOLD IS 0                                =20
*+       ENABLED                                            =20
*+       ERROR THRESHOLD IS 5                               =20
*+       ISA SIZE IS 0                                      =20
*+       LANGUAGE IS COBOL                                  =20
*+       MPMODE IS SYSTEM                                   =20
*+       NOMAINLINE                                         =20
*+       MULTIPLE ENCLAVE IS ON                             =20
*+       NEW COPY IS ENABLED                                =20
*+       OVERLAYABLE                                        =20
*+       PROGRAM                                            =20
*+       NOPROTECT                                          =20
*+       QUASIREENTRANT                                     =20
*+       NONRESIDENT                                        =20
*+       REUSABLE                                           =20
*+       SAVEAREA                                           =20
*+       .                                                  =20
=20

Gary Cherlet
Justice Technology Services
Department of Justice, SA Government

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

Gary says: Boycott Apple - the hardware company that puts software companie=
s out of business!=20
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.

Outcomes