Re: Change commitment control after compilation -- RPG400-L

Dieter,

It all depends on how you see the world. I have to see it from what is
actually running out there and I provide “additional” software to shops
that doesn’t run journaling as a default so I have to cope with that fact.

Besides that I target the RPGLE world where people that have no intentions
to use either JAVA or C and still define their DB2 with DDS.

Both DDS and RLA are two IBM I only features that has capabilities that SQL
doesn’t have. SQL can’t insert new fields in rows but only append, it has
no EDTCDE or EDTWRD facilities etc. etc. SQL has no native specific record
lock but only commit on joined data sets – all in all SQL has lacks in
comparison to RLA/DDS.

However SQL has some very advanced features that RLA/DDS doesn’t have
especially in presenting data. I believe that a modern UI can’t be
constructed without using SQL and for that reason I use SQL in all my
REST/CRUD services that by the way delivers raw XML, JSON or JSON Data
Stores – all written in RPGLE that supports V5R3+.

You may wonder what a JSON Data Store is but it is actually very similar to
how we experience a DB2 *FILE object, the JSON object starts with a
description of the JSON data within it and then contains the data set
itself or in other words it is a self-described data object.

One other benefit in DB2 SQL is that it has and can process data by RRN
where you in many other SQL based DB has to process data by a set of fields
that together forms a unique identification of the record/row.

So I have a very practical approach to what I do and to the environments I
have to service or if you like run side by side and I do believe that
trying to introduce commitment control in blindness of an environment I
have no control of whatever may cause overall damage to the system.

To me we are out in a discussion where all fields should be made NULL
capable and defined in CCSid 1208 (UTF-8) because it theoretical possible
(Yes, IBM I DB2 supports UTF-8 in DB2) however that is not how the real
world looks like and any product that has such requirements are dead born.

On Thu, Dec 19, 2013 at 10:18 PM, D*B <dieter.bender@xxxxxxxxxxxx> wrote:

<Buck>
So I gave an example of an
old program I actually work with to start the discussion.
</Buck>
Thatt's a very interesting point of view, and we could continue the
discussion (just ignoring that some people don't want to understand...).
Might be far away from my todays work, but I'm interested too. I see two
aproaches: first is to leverage modularisation, to try to use the ability
of using diffrent connections (= ACTGRP in this context), or to try to use
transaction control in an animal like this with cycle and Level break
functionality; latter was a little bit strange to me, but I'm getting warm,
let's continue, if you want!

Dieter

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.