RE: How can I speed up the copying of data using DDM and field selection.

I would guess that "SOX restriction" comes from their internal SOX
governors. We are also under SOX and the restriction is that we can't
update production LIBRARIES. We all have our own non-prod libraries that we
use for extracting / analyzing data, creating temp programs, queries, etc.

As developers, we are constantly pushing back to the "intent" of SOX, not
the "interpretation" as they see it. Sometimes we win, sometimes we lose.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob
Berendt
Sent: Thursday, August 10, 2017 3:02 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: How can I speed up the copying of data using DDM and field
selection.

SAVRSTOBJ might be faster if only because there's no intelligence in
transferring the data. However you will have the transferring time, the
wasted space of ALL the rows on the target, and the time involved doing the
trimming on the target. I don't think it's the answer to this solution.

Another person also suggested creating a temporary file on the source
containing only the desired rows, and then transferring that. But
apparently even this temporary table goes against their SOX restrictions.
Apparently they are allowed READ only to the source system and any other
process, ran by them or others, is perceived to be other than a read
operation.

Here's the important part:
"appears" to go against their SOX requirements the key word being "appears".
We're subject to SOX and I fail to see that anywhere in the SOX regulations.


Rob Berendt