A new logonid was created for TMON with a UID and GID so that it can use USS services.
An error shows in ACFRPTOM that the logonid does not have a complete omvs profile
CA Mainframe Security - US / z / OS Event Log - PAGE1
initUSP TMONID OMVSGRP N / A N / A 8 8 24
25/03/19 19.084 9.31.26 TMONID SYSX SYSX
Failed - User incompletely defined as OpenMVS user
A SHOW OMVS command was issued and it showed the UID and GID are both defined.
8/8:24 for initusp request means that the user is not correctly setup for OMVS processing.
If the user and group profiles are setup correctly and show in SHOW OMVS output as a valid UID and GID that was defined ,
check to see if the user has NO-OMVS.
If NO-OMVS is set on the logonid it means that the user is not allowed to use omvs.
The resolution is to remove NO-OMVS
CHANGE logonid NONO-OMVS
Details of the NO-OMVS field can be found in docops.
Specifies that this user cannot use any z/OS UNIX System Services. NO-OMVS overrides any user OMVS profile record defined for the user. This user cannot use the defaults specified in the DFTUSER or DFTGROUP fields of the GSO UNIXOPTS record. (Bit field)