We just installed v2.2.0 and are now seeing these messages:
ICH408I USER(XXXXX ) GROUP(XXXX) NAME(XXXXX)
CL(PROCACT )
INSUFFICIENT AUTHORITY TO GETPSENT
EFFECTIVE UID(####) EFFECTIVE GID(####)
IBM has an info apar "II11813" that addresses the PROCACT class, but we can't implement the circumvention because our userids have to have the UAUDIT flag on.
We are wondering what the SFTP client or server is doing now to cause these messages and wondering if there is some way to setup SFTP to avoid them?
INSUFFICIENT AUTHORITY TO GETPSENT
Re: INSUFFICIENT AUTHORITY TO GETPSENT
Co:Z SFTP now reports (by default) the cpu time spent in its ssh child process. This is an informational (I) level logging message. If you wish to avoid this RACF notification, which is an informational message only, either export COZ_LOG=N or set the loglevel=N option inside sftp.
We plan on making this a debug level message in the next release of Co:Z.
We plan on making this a debug level message in the next release of Co:Z.
Re: INSUFFICIENT AUTHORITY TO GETPSENT
Thanks, I used lzopts loglevel=N to circumvent the ICH408I message. Unfortunely it took away a few of the log messages that used to show up, but we can live with that until the next release when the default changes. Thanks.
Re: INSUFFICIENT AUTHORITY TO GETPSENT
FYI - the new release of the Co:Z Co-Processing Toolkit (2.3.0) is now available, and it changes this message level from (I)nfo to (D)ebug
Update: this didn't actually happen.... the message level wasn't changed until 2.4.0
http://dovetail.com/docs/cozinstall/changes.html
Update: this didn't actually happen.... the message level wasn't changed until 2.4.0
http://dovetail.com/docs/cozinstall/changes.html
Re: INSUFFICIENT AUTHORITY TO GETPSENT
Just a follow up -
These "audit" messages will still occur if you enable debug-level logging or finer and you have UADIT enabled.
IBM has just released PTFs for the following APAR which address / eliminate these:
http://www-01.ibm.com/support/docview.w ... sg1OA42264
These "audit" messages will still occur if you enable debug-level logging or finer and you have UADIT enabled.
IBM has just released PTFs for the following APAR which address / eliminate these:
http://www-01.ibm.com/support/docview.w ... sg1OA42264