Connecting Omegamon for z/OS and the RMF Task 'GPMSERVE'.

book

Article ID: 16287

calendar_today

Updated On:

Products

CA ACF2 CA ACF2 - DB2 Option CA ACF2 for zVM CA ACF2 - z/OS CA ACF2 - MISC CA PanApt CA PanAudit

Issue/Introduction

Initiating a connection between Omegamon for z/OS and the RMF Task 'GPMSERVE'.



To initiate a connection between Omegamon for z/OS and the RMF Task 'GPMSERVE', which uses PassTickets, a SAF Trace of 'GPMSERVE' may show:

==============================================================================

SMFID= AAWR TOD= 14:27:40.99 TRACEID= PT USERID= SS#$ 

JOBNAME= RMFSERVE ASID= 0099 PGM= BPXPTATT CURR RB= BPXPTATT 

SFR/RFR= 8/48:0 MODE= TASK APF= AUTHORIZED LOCKS= NONE 

SAFDEF= VERIFY INTERNAL MODE= GLOBAL 

 

RACROUTE REQUEST=VERIFY,REQSTOR='SAFOEACE',RELEASE=7760,SYSTEM=YES, 

SESSION=OMVSSRV,SECLABL='........',STAT=ASIS,SMC=YES, 

ACEE=00000000,APPL='GPMSERVE',ENVIR=CREATE,ENCRYPT=YES, 

ERROROPT=ABEND,LOG=ASIS,MSGSP=0,MSGSUPP=YES,NESTED=NO, 

PASSCHK=YES,PASSWRD='*SUPPRESSED*',USERID='OMG',WORKA= 

==============================================================================

...and the RACF Reason Code 48, in the 'SFR/RFR= 8/48:0' line above, the explanation given of the RACF Reason Code '48' doesn't make it easy to resolve this problem. What does it really mean?

 

Environment

z/OS, ACF2 for z/OS.

Resolution

The installation of Omegamon to use RMF, to communicate, the Omegamon Sub System ID will run as a Started Task. This means that ACF2 will require this Omegamon Sub System to have the 'STC' bit turned on. But, with the PassTicket support turned on and when GPMSERVE engages with the Omegamon Sub System, ACF2 will get an error. Basically, an ID with the 'STC' bit can't be used to authenticate as an ID that logs on. You will need to remove the 'STC' bit and set a switch in the Global Systems Options (GSO) to allow this ID to run as a Started Task and also a Logon. Therefore, this means the STC GSO Record needs to be used.

Additional Information

In summary:

1.) Don't put the 'STC' bit on, on the Logonid.

2.) In the STC Record, make the LOGONID() and the STCID() both be the same, matching the Procname and the Logonid.