As part of the impending phase out of the i where I work, I have been
told that access to functions currently authorized needs to be changed
at midnight on 10/31.
Two files, only second needs to be changed. First is user related
which associated with the second where a record exists for each
function to be allowed.
I can see how to write an RPG program to do this. Just work with the
second file. Read record, if authorized function is in a list, delete
the record, if the person authorized is not one specific person.
Makes for a big nested if. I think there are 20 or so functions that
have to be removed.
I could see creating a file with those functions in it, to make the IF
less of a potential issue.
I am wondering if SQL would be a better choice. And, if so, whether
the SQL could be put in a job that is subitted on hold to be released
later - or just released at a set time.
Would this be where RUNSQLSTM (not sure that is the right command - I
am away from the i right now) would be used? We have SQL installed.
My limited SQL skills would be something like this:
DELETE FROM BSYSQSP2 WHERE QSSEC2 <> 'xxxx' AND QSFN01 = 'FUNCTION'
Repeat the above for all functions.
So, is there a difference between the RPG method and SQL method? Are
separate DELETE commands the way to go in SQL?
This looks like my last programming task. Just want to do it right
and maybe learn something in the process.
It has been a fun ride. I will definitely miss working with the i,
despite the name changes.
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
This mailing list archive is Copyright 1997-2013 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact