RC=8/8:44 and RC=8/8:48 R_datalib calls in ACFRPTOM
search cancel

RC=8/8:44 and RC=8/8:48 R_datalib calls in ACFRPTOM

book

Article ID: 26481

calendar_today

Updated On:

Products

ACF2 ACF2 - z/OS ACF2 - MISC

Issue/Introduction

In the ACF2 ACFRPTOM report there are numerous entries with R_datalib calls that are getting RC=8/8:44 and RC=8/8:48.

Everything is working fine, what do these entries indicate?

 

Sample ACFRPTOM report entry:


SERVICE USERID GROUP UID GID SAF RC RSN
DATE TIME JOBNAME SOURCE SYSID CPU
R_datalib xxxxxx OMVSGRP 0 1 8 8 48
12/17/23 03.351 17.16.05 xxx SYSx xx
Failed - An output area was not long enough

 

Sample OMVS SECTRACE entry:


CAS2206I Function=DataGetFirst ,Userid=xxxxxx
CAS2206I Ring Name=KeyringName
CAS2206I Cert Flag=0002 len=030C ptr=0F0EE038
CAS2206I Label=Label
CAS2206I SDN len=00000087 ptr=0F0EE3E0
CAS2206I Record ID len=00000030 ptr=CERTAUTH
CAS2205I REQUEST=R_datalib ,EXIT=POST,RC=8/8:48

Resolution

The R_datalib calls that are getting RC=8/8:44 and RC=8/8:48 are related to the processing of digital certificates and keyrings and are normal.

The RC=8/8:44 on a REQUEST=R_datalib Function=DataGetNext call in the ACFRPTOM report or the OMVS SECTRACE is normal. The entry indicates that an attempt was made to get the next certificate on the keyring but all the certificates had been retrieved, so there is no "next" certificate at that point and the caller gets an 8/8:44 to indicate the end of the keyring.

The RC=8/8:48 on a REQUEST=R_datalib Function=DataGetFirst call in the ACFRPTOM report or the OMVS SECTRACE is not a problem. The 'get' is issued initially with a certain sized buffer. If it is not big enough for the certificate then the 'get' is reissued with a larger buffer.