|
Works for me
On Wed, Jan 29, 2014 at 5:23 PM, Charles Wilt <charles.wilt@xxxxxxxxx>wrote:
I pull it down via FTP
Charles
On Tue, Jan 28, 2014 at 11:14 PM, Evan Harris <auctionitis@xxxxxxxxx>
wrote:
OK, I'll bite - how do they send you the file ?(presumably)
On Wed, Jan 29, 2014 at 5:10 PM, Charles Wilt <charles.wilt@xxxxxxxxx
wrote:want
The vendor doesn't get any rights on my system at all :)
Charles
On Tue, Jan 28, 2014 at 6:45 PM, Evan Harris <auctionitis@xxxxxxxxx>
wrote:
Hi Buck
thanks for sharing your thinking. My view point was that I would not
them to be able to get near the customer master file as it
otherhasthe
customers from other vendors.
I would think that the vendor would need at least *MANAGE rights over
wrote:file they provide, but no rights at all (*EXCLUDE) over the table thedata
is going into or other tables in the same library.
On Wed, Jan 29, 2014 at 12:05 PM, Buck Calabro <kc2hiz@xxxxxxxxx>
berequirementsOn 1/28/2014 5:20 PM, Evan Harris wrote:
I'm a bit surprised that you would have the same security
on
the staging tables as a production table.
It seems to me that tables that are part of an application should
fromgoverned by the application security model, and I normally work
having
PUBLIC *EXCLUDE, or *PUBLIC *READ as my preferred model - all
thetheaccesssecurity -
being via the application interfaces.
In my experience, staging tables often require lower levels of
for example having a specific user having *MANAGE rights, or even
name,preferenceability to create a table in the IFS or in a library, so my
istables
to have this "cordoned off" in a separate library.
Or maybe I'm just misunderstanding the usage of the term staging
in
this context.I was thinking of a staging table as an import; say a vendor is
exchanging customer information with you. They send a file with
thataddress, birth date and mailing preferences and you write a program
matches the incoming data to your own customers so you can update
proprietarycustomer master file.
If your company considers customer name and address to be
shouldviaenough that you want to secure it in the customer master file (say
*EXCLUDE and adopted authority) then the incoming 'work' table
productionbe
subject to the same security requirements. It might not have your
customer ID number on it, but it's still customer name and address
information that's in the incoming work file...
--buck
I can't imagine staging tables with the same layout as
tables.isn'ttables. By that I mean that generally speaking, inbound data
decimaltypically normalised. Or free of decimal data errors (commas,
dashespoints, minus signs and currency symbols in amounts, slashes or
the...in dates, etc.) So in my case, I always use different names for
raw input as opposed to the final destination, production
Imailing
stagingkeep them in the same library because they have similar security
requirements. If I don't want someone peeping at birth dates in
production, I probably don't want them peeping at them in a
mailing--table, no matter how transient that data may be.
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
Regards
Evan Harris
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
listlistlist
To post a message email: MIDRANGE-L@xxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
Regards
Evan Harris
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
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: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.