Testing BMC AMI Defender

You can test that BMC AMI Defender is working correctly by performing the following procedures:

Testing BMC AMI Defender as a job

To test that BMC AMI Defender as a job, perform the following steps:

Open amihlq.CZAGENT.CNTL(CZAGENT) and customize according to the instructions provided in the data set member.
The amihlq variable represents the high-level qualifier that you used for installation.
Open amihlq.CZAGENT.CNTL(CZAGNJOB) and customize according to the instructions provided in the data set member.
Ensure that the //CZAPARMS DD statement references the correct parameter data set.
Submit the CZAGNJOB job.
- If the job does not end, check the job log for errors.
- If you receive a JCL error or if CZAGNJOB completes immediately, see the messages in the CZAPRINT SYSOUT data set to resolve the error. If you cannot resolve the problem, contact BMC Support.
In the SDSF, enter the following command:
/F <jobName>,STATS(SEND)
The jobName variable is the name that you chose for the CZAGNJOB job statement.
Check your server or syslog console or server for syslog messages with BMC AMI Defender statistics. Also check for TSO logon messages and security violation messages.
If no TSO logon or security violation messages appear, exit your TSO session and log in again. If a message reporting your logon still does not appear on the syslog console or server, contact BMC Support.
To stop the agent, enter the following command in SDSF:
/P <jobname>
The job should end normally.
Note
Do not issue the “P” as a line command in SDSF.

To test that BMC AMI Defender as a job, perform the following steps:

Open the sample job in amihlq.CZAGENT.CNTL(CZAGNJOB).
The amihlq variable represents the high-level qualifier that you used for installation.
Change the job statement to conform to your installation standards.
Example
Change all instances of amihlq with your high-level qualifier.
Ensure that the //CZAPARMS DD statement references the correct parameter data set.
Submit the CZAGNJOB job.
- If the job does not end, check the job log for errors.
- If you receive a JCL error or if CZAGNJOB completes immediately, see the messages in the CZAPRINT SYSOUT data set to resolve the error. If you cannot resolve the problem, contact BMC Support.
In the SDSF, enter the following command:
/F <jobName>,STATS(SEND)
The jobName variable is the name that you chose for the CZAGNJOB job statement.
Check your server or syslog console or server for syslog messages with BMC AMI Defender statistics. Also check for TSO logon messages and security violation messages.
If no TSO logon or security violation messages appear, exit your TSO session and log in again. If a message reporting your logon still does not appear on the syslog console or server, contact BMC Support.
To stop the agent, enter the following command in SDSF:
/P <jobname>
The job should end normally.
Note
Do not issue the “P” as a line command in SDSF.

Before you begin, ensure that the data set in the //STEPLIB DD of the CZAGENT procedure is APF authorized.

To test BMC AMI Defender as a started task, perform the following steps:

Open the sample procedure in amihlq.CZAGENT.CNTL(CZAGENT). You can see an example in the Running-BMC-AMI-Defender-as-a-started-task topic.
The amihlq variable represents the high-level qualifier that you used for installation.
Replace amihlq with your high-level qualifier.
Ensure that the //CZAPARMS DD statement refers to the amihlq.CZAGENT.CNTL data set as a whole, not to a particular member.
Check the CZADIAG and CZAPRINT DD statements. They should refer to a held SYSOUT class.
Copy CZAGENT to a data set in your SYS1.PROCLIB concatenation.
In SDSF, enter the following command:
/S CZAGENT
If the CZAGENT started task does not appear in the SDSF DA panel, enter PREFIX CZA* or OWNER *. If it does not appear, check the H and O panels.
Check the CZAPRINT data set.
- If errors appear, try to resolve them and restart CZAGENT.
- If errors do not appear, perform Testing BMC AMI Defender as a job.