Setup of started tasks

zSecure Alert must run as a started task. Copy the C2PCOLL and C2POLICE procedures from SCKRPROC, and your zSecure Alert-enabled zSecure configuration members, to a started task procedure library on the system where you are going to use zSecure Alert. When copying these procedures you can choose different names:

For the zSecure Collect started task, the name that you choose is the one you specify during Alert configuration. See the section about specifying general settings during Alert configuration in the zSecure Alert User Reference Manual.
Please note that zSecure Collect is executed with parameter UNIX=YES, which might result in additional RACF SMF type 80 success records being generated. This depends on your RACF SETROPTS and UAUDIT settings:
- If SETROPTS AUDIT(FSOBJ) has enabled command auditing for the FSOBJ class, RACF will write SMF records for successful CHDIR events that are performed during zSecure Collect processing.
- If SETROPTS LOGOPTIONS(ALWAYS(DIRSRCH)) has set the auditing options for the DIRSRCH class to always log events, RACF will write SMF records for successful DIRSRCH events that are performed during zSecure Collect processing.
These classes (FSOBJ or DIRSRCH) need not be active to control auditing.
Depending on the size of your z/OS UNIX file system, the number of SMF records that are produced could be large.
For the zSecure Alert address space, where the default is C2POLICE, use the name as specified in the C2POLICE parameter in the zSecure configuration.
In both procedures, you must specify your Alert-enabled zSecure configuration.
In the zSecure Alert JCL, you must update the PPARM parameter to reflect the name of the Alert configuration with which you intend to run. The PPARM parameter must be equal to the zSecure Alert configuration name, with a P appended. You can also use a system symbol in the name of the zSecure Alert configuration to be used. For example, you might change
```
   // PPARM=C2PDFLP        C2POLICE parameter member <setname>P
```
to
```
   // PPARM=&SYSNAME.P     C2POLICE parameter member <setname>P
```
If you further customize the JCL, make sure that you do not include an OUTPUT statement with DEFAULT=YES and an OUTDISP of PURGE or HOLD. Doing so prevents all email and text message alerts from being sent.