END TRANSACTION Needed with Oracle?

, ,
1

Hi Friends,

Have queries on Natural/Oracle under Unix platform. Curious if ET (END TRANSACTION) is really needed for Oracle database?

I wrote a simple code:

DEFINE DATA
LOCAL
1 EMP VIEW OF EMPLOYEE
2 EMP_ID
END-DEFINE

SELECT * INTO VIEW EMP
FROM EMPLOYEE
WHERE ACCOUNT_ID = 1234567890
DISPLAY EMP
*
MOVE 2222222222 TO EMP_ID
UPDATE
END-SELECT

SELECT * INTO VIEW EMP
FROM EMPLOYEE
WHERE ACCOUNT_ID = 1234567890
DISPLAY EMP
END-SELECT
*
END

Output:

  1. In 1st DISPLAY I got EMP_ID as 1111111111 (the initial database value)

  2. In 2nd DISPLAY I received EMP_ID = 2222222222

Means the value was updated in Oracle database without ET (I queried dabase as well thru other software and got the updated value).

Can anyone throw some light on this as curious on why our past programmers have coded ET logic in every UPDATE? And how will it cost as far as CPU usage is concern.

Also,

  1. Since there is no ADABAS, no TT will come in picture so how does HOLD queue time and record limit etc comes in picture for this case? or how does UPDATE works for Oracle?
2

A qualified guess would be that the Natural parameter ETEOP
(ET at End Of Program) is set to true ?!
Finn

3

Hey Finn,

Can I know where should I look for the settings? I tried GLOBALS but no luck.

4

It’s in the natural parameterfile.
So use the natparm program, select the relevant parmfile
and then it’s in Database Management /General Parameters

Finn

5

Hi Finn,

Thanks for your valuable note.

I tried this but no luck. Received below screen but nowhere ‘general parameters’ found. I tried to search the ETEOP but :frowning:

05/11/2009 ±------------------------------+ User: (Config)
22:56:30 | ADABAS Parameters | File: NATPARM
| Batch Mode |
±---------------------| Buffer Sizes |-----------------------+
|File Edit | Character Assignments | Search |
±---------------------| Compiler Options |-----------------------+
| Database Management System |
| DCOM Support |
| Devices… |
| Environment Assignments |
| Error Handling |
| Function Keys |
| Limits |
| Miscellaneous |
| Product Configuration… |
| Program Loading and Deletion |
| Remote… |
| Report Parameters |
| System Files |
| System Variables |
| Work Files |
| Year 2000 Support |
±------------------------------+
Year 2000 Parameters (DFOUT, DFSTACK, DFTITLE, YSLW)

6

We are using Natural V5.1.1 on Unix

7

Hi Ats,
I don’t have an (ancient;-) 511 available, and neither the documentation…
but in your screenshot above there is a "Database Management System "
menu item - have you explored that ?
Finn
PS Current Natural version is 6.3.7 - considering an upgrade ?!

8

Yes Finn,

I checked that option and found nothing.

9

After a little googling for an old manual I found that the ETEOP parameter is new in 6.1.1.

  • so that explains it’s absence in you parm :wink:

Before 611 it was handled by the OPRB parameter!

Have a look at the description of the OPRB in you 5.1.1 manual or see the enhancement in the 611 doc here:
http://itmdapps.milwaukee.gov/citygov/natural421/rnarchive/nat611win.pdf

Finn

10

Got it Finn!!!

Thanks a lot!