RE: Another FieldProc question -- MIDRANGE-L

We use CryptoComplete and FieldProcs. Regardless of the user's authority to the encrypted value, nothing happens to the field value if it's not changed when other fields are. In our system, we have 3 levels of authority - not authorized to see any portion of the field, authorized to see last 4 digits and authorized to default to last 4 digits but have an available button that allows entire field to be unmasked. Only users that are authorized to see the entire contents have the ability to modify the field. The field would be read only until they've pressed the button/fkey that allows them to see the unmasked value and then they could modify the value and it's written to the file while it's unmasked.

Linoma/Help Systems has programs available that you call that can be used to control the unmasking/re-masking of an encrypted field. We've been using the software for over a year and haven't had any problems. It's pretty easy to work with and their support (at least when it was Linoma) is excellent. If you have the budget available, I would suggest getting a few hours of online training. We worked one on one with one of their people and he did a great job explaining how it all works and helping with any questions that came up.

If you have any additional questions, feel free to email me offline.

----------------------------------------------------------------------

message: 1
date: Thu, 30 Aug 2018 10:08:25 -0700
from: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
subject: Another FieldProc question

Ladies and Gentlemen:

Suppose a file has a FieldProc (we'll assume, for now, that it's from Crypto Complete) on a field. And suppose some users are authorized to see the complete field contents, others are authorized to see partially redacted field contents, and others are not authorized to see the field at all.

Let's also assume that the FieldProc is not some total botch job.

Now suppose user JSMITH, who is not authorized to see the field at all, changes a record in the file, and user JDOE, who is authorized to see partially redacted contents, each change a record. In neither case do they enter a new value for the field that has the FieldProc on it.

What happens to the value of that field?

And what happens to it if they DO enter new values for it?

--
JHHL

------------------------------

message: 2
date: Thu, 30 Aug 2018 17:15:15 +0000
from: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
subject: RE: Interactive SQL with concatination

My first comment is that || for concatenation isn't recommended (should use CONCAT). Normally the problem is CCSID, but that shouldn't be the issue is both jobs are 37.

So the only difference is whether the || appears at the end of beginning of the line? My 7.3 runs both fine.

-----Original Message-----
From: Don Brown [mailto:DBrown@xxxxxxxxxx]
Sent: Wednesday, August 29, 2018 6:25 PM
To: MIDRANGE-L <midrange-l@xxxxxxxxxxxx>
Subject: Interactive SQL with concatination

This is weird ...

There are two SQL statements below, the first gives an error and the second does not.

These were entered in the STRSQL on a V7R3 system current on PTF's as at June 2018

The only difference is the positioning of the concatenation.

Job CCSID is 37

Why is this so ?

Both run in ACS Run SQL Scripts

select substr(digits(dtrtdt),1,4) || '-' ||
substr(digits(dtrtdt),5,2) || '-' ||
right(digits(dtrtdt),2) as iso_date from mfsdtrpf
Token was not valid. Valid tokens: ( + - ? : DAY INF LAG NAN RID R

select substr(digits(dtrtdt),1,4) || '-'
|| substr(digits(dtrtdt),5,2) || '-'
|| right(digits(dtrtdt),2) as iso_date from mfsdtrpf SELECT statement run complete.

Don Brown

------------------------------

message: 3
date: Thu, 30 Aug 2018 13:22:23 -0400
from: "Art Tostaine, Jr." <atostaine@xxxxxxxxx>
subject: Re: SQL View question

RID is like a record key so the group by doesn't work.
I took the group by out of the view and added RID.

Here is view
create view InvPhy (rid,shp,sea,sty,clr,fab,mod,msz,qty) as
(SELECT ls.rid,ls.shp,ls.sea,ls.sty,ls.clr,ls.fab,ls.mod,ls.msz,ls.qty
FROM invdta.locsku00 as ls);

Here is my select says RID or expression in select list not valid

select * from INVPHY
where rid = 81251501 and shp=50875 and sty= 'J4LW2700'
group by shp,sea,sty,clr,fab,mod,msz
order by shp,sea,sty,clr,fab,mod,msz

[SQL0122] Column RID or expression in SELECT list not valid. [SQL
State=42803, DB Errorcode=-122]

On Thu, Aug 30, 2018 at 12:57 PM Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:

or include RID in the SELECT clause and the group by...

Results would be the same...

Charles

On Thu, Aug 30, 2018 at 10:36 AM <dlclark@xxxxxxxxxxxxxxxx> wrote:

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 08/30/2018
12:06:02 PM:

I have a SQL Statement in an RPG Program that uses fields that aren't

in

the group by as selections. Something like this where field RID is

used

to

select.

When I try to create it as a view I can't access RID.

You have to leave the group by out of your view and include the
rid column in the view's result set. Then do the group by at the time

you

consume the view.

Sincerely,

Dave Clark
--
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300

Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331

*********************************************************************************************

This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary
information. If you have received this message in error, please
immediately notify the sender and delete and destroy the message and all
copies. All unauthorized direct or indirect use or disclosure of this
message is strictly prohibited. No right to confidentiality or privilege
is waived or lost by any error in transmission.

*********************************************************************************************

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.midrange.com%2Fmailman%2Flistinfo%2Fmidrange-l&data=02%7C01%7Clinda.wagner%40conduent.com%7C8850d8811b814d539abe08d60e9ea52e%7C1aed4588b8ce43a8a775989538fd30d8%7C0%7C0%7C636712471867358774&sdata=vuCORXnr%2FU6PRdcSXHvexdYNyfek5GBPTotKwup8hMg%3D&reserved=0
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchive.midrange.com%2Fmidrange-l&data=02%7C01%7Clinda.wagner%40conduent.com%7C8850d8811b814d539abe08d60e9ea52e%7C1aed4588b8ce43a8a775989538fd30d8%7C0%7C0%7C636712471867358774&sdata=QXkMAxr1X98hy2oWGUsRq%2Bjn98cQIwRxy%2Ftz0bn6%2Bgg%3D&reserved=0.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Famzn.to%2F2dEadiD&data=02%7C01%7Clinda.wagner%40conduent.com%7C8850d8811b814d539abe08d60e9ea52e%7C1aed4588b8ce43a8a775989538fd30d8%7C0%7C0%7C636712471867358774&sdata=Lv5yo1AzHc8WiC9pZYPsURueQ38ZHAsVWubu4yqHGvw%3D&reserved=0

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.midrange.com%2Fmailman%2Flistinfo%2Fmidrange-l&data=02%7C01%7Clinda.wagner%40conduent.com%7C8850d8811b814d539abe08d60e9ea52e%7C1aed4588b8ce43a8a775989538fd30d8%7C0%7C0%7C636712471867358774&sdata=vuCORXnr%2FU6PRdcSXHvexdYNyfek5GBPTotKwup8hMg%3D&reserved=0
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchive.midrange.com%2Fmidrange-l&data=02%7C01%7Clinda.wagner%40conduent.com%7C8850d8811b814d539abe08d60e9ea52e%7C1aed4588b8ce43a8a775989538fd30d8%7C0%7C0%7C636712471867358774&sdata=QXkMAxr1X98hy2oWGUsRq%2Bjn98cQIwRxy%2Ftz0bn6%2Bgg%3D&reserved=0.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Famzn.to%2F2dEadiD&data=02%7C01%7Clinda.wagner%40conduent.com%7C8850d8811b814d539abe08d60e9ea52e%7C1aed4588b8ce43a8a775989538fd30d8%7C0%7C0%7C636712471867358774&sdata=Lv5yo1AzHc8WiC9pZYPsURueQ38ZHAsVWubu4yqHGvw%3D&reserved=0