IBM Security Z Security

Hi james,

this message is the result of no "SET C2PCUST=" in a configuration or it being commented out. As you are showing a C2R$PARM with one it, my guess would be you are not using this particular config member in the UI.

You can check which one you are using in the zSecure User Interface like this

Start zSecure

Type "DDLIST" on the command line and enter

Type "M C2R$PARM" on the command line and enter.

it will then search every dataset allocated for that member. You can view it and my guess would be its not the one you expected and there is no "SET C2PCUST" statement in there 

cheers

rene

To expand on what Rene wrote, the C2POLICE started task takes C2R$PARM from the PROCLIB (or STCPROC) concatenation.  Most customers copy a member C2R$PARM into a PROCLIB data set, just like they copy C2POLICE, C2PCOLL, C2PACMON, CKQRADAR, etc. from SCKRPROC to their PROCLIB.

The ISPF part of zSecure takes C2R$PARM from the CKRPARM data set, specified in the CKR command.

So there are 2 members with the same name, you have to ensure changes are applied to both, as needed.  Using xxxx.PROCLIB as your CKRPARM data set is not practical, as there are several zSecure configuration members in CKRPARM. 

Some (not many!) installation include the CKRPARM and SCKRPROC data sets in their PROCLIB concatenation, so all zSecure procs (C2RC, etc) are accessible to batch jobs and START commands, and the CKR$PARM member is shared, but that means 2 extra PROCLIB data sets and lots of deadwood (members).  Most installations copy half a dozen members into a PROCLIB data set, manually synchronize changes and use // JCLLIB commands to point JCL to the CKRPARM and SCKRPROC data sets.