Violation - Function DataGetFirst - An output area was not long enough
Article ID: 122698
Updated On:
Products
Endevor
Endevor Natural Integration
Endevor - ECLIPSE Plugin
Endevor - Enterprise Workbench
Issue/Introduction
We started the web services endevor https in a new z/OS TSS environment.
This time the security experts have activated a trace in the USS and noted the error in object:
Failed - An output area was not long enough Function:
DataGetFirst Userid: ZWSE
Ring name: ZWSEKeyring
We would like to understand the meaning of this error and know how to correct it
This time the security experts have activated a trace in the USS and noted the error in object:
Failed - An output area was not long enough Function:
DataGetFirst Userid: ZWSE
Ring name: ZWSEKeyring
We would like to understand the meaning of this error and know how to correct it
Environment
Z/OS
USS
USS
Resolution
From our TSS base, I found this explanation:
A RC=8/8:48 on a REQUEST=R_datalib Function=DataGetFirst call in the report or the SAF security trace is NOT a problem.
The 'get' is issued initially with a certain size buffer.
If it is not big enough for the certificate then the 'get' is reissued with a larger buffer.
This is NOT a problem.
Also in some case, creating a new KEYRING for this certificate could avoid this.
A RC=8/8:48 on a REQUEST=R_datalib Function=DataGetFirst call in the report or the SAF security trace is NOT a problem.
The 'get' is issued initially with a certain size buffer.
If it is not big enough for the certificate then the 'get' is reissued with a larger buffer.
This is NOT a problem.
Also in some case, creating a new KEYRING for this certificate could avoid this.
Feedback
Yes
No
Powered by
