How does CA ACF2 use the GSO option STAMPSMF and what are the implications to CA-7?
Article ID: 27074
Updated On:
Products
Issue/Introduction
What field and how many bytes are used for the GSO option STAMPSMF?
What happens to the CA-7 data and what will CA-7 do?
Environment
Component: ACF2MS
Resolution
If the ACF2 GSO OPTS record has the option STAMPSMF turned on, ACF2 will update ALL SMF records on the system with the logonid.
The field is the User Identification field which has varied names depending on what the SMF record is.
The field names that are updated are JMRUSEID or JCTUSEID. SMF will then propogate this field value to SMF30RUD (for type30 SMF records) or any other SMF record field that references USERID.
Since Logonids are 8 bytes long, that is the length updated.
No extra space is used for STAMPSMF. According to CA-7 support, if the ACF2 option is turned on, and the default CA-7 setup is used, then CA-7 will be unable to track jobs since ACF2 does it's update last and will overlay anything CA-7 puts in the SMF field. So if STAMPSMF is used with CA-7, you will need to update the L2OPTS DD in the CAIRIM proc to use the RdrTime (20) instead of UserId (80).
After the L2OPTS DD sysfile update, you will need to restart CAS9.
Feedback
