Requirements

[John Earl <johnearl@xxxxxxxxxxx>]

> 8.) Requirements seemed woefully weak overall.  Not very many and not many
>   juicy ones.  I'm not sure if this is good news or bad.  Good meaning things
>   are in good shape and IBM is doing the right thing, bad meaning we didn't
>   get much in on this opportunity to present our case to IBM....
 
Hmmmm...  We've got a lot of brain power here, maybe we can have
a Midrange-L requirements process.  :^)

I'll start the bidding with these two....

1)    I'd like a user controlled flag on that allows me to turn off *PUBLIC authority for a given user, or job, or device.  My goal here is to be able to have a class of user  (maybe called *Internet) that I can restrict from getting authority from the *PUBLIC setting.  This would be of great use to all of those shops that have vendor packages that grant *PUBLIC too much authority, but don't have the knowledge/daring to figure out how to properly secure the application.  This would help ensure that my ANONOMOUS FTP profile was _really_ restricted to a given set of files.

2)    Now that we can FTP save files across the net, isn't it time that the LODRUN command supported *SAVF's?

Just my 2 cents

jte
 

 
 

--
John Earl   PowerTech Toolworks
johnearl@toolnet.com  www.toolnet.com
253-858-7388   206-575-0711
PowerLock Network Security for the AS/400
--
  +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---