Can anybody tell me why the QSPCRTSP API is shipped with *PUBLIC *EXCLUDE authority, when other spooled file API's are set to *USE I need to use this API to develop a DUPSPLF command, and would like a watertight case to present to my Security Officer when I ask him to set the authority to *USE.
Unconfigured Ad Widget
Collapse
Announcement
Collapse
No announcement yet.
QSPCRTSP default authority
Collapse
X
-
QSPCRTSP default authority
Nick, I am not certain why the API is set this way but you might be interested in an article published by Midrange a few months back, around December. The article contained a command JWSPLF which I have found is very useful. It supports archive/re-print and several other features. If security is a big issue in this case, you may want to set up a user/owner program that your security officer creates to access the API. Make sure that that program qualifies all calls. David Morris
Comment