BPX messages precede GLA messages in the z/OS SYSLOG

In the z/OS® SYSLOG, messages with the prefix BPX precede the z/OS Log Forwarder messages, which are messages with the prefix GLA.

Symptom

When the z/OS Log Forwarder starts, the z/OS SYSLOG includes the following messages:

S GLAPROC
BPXM023I (GLALGF) GLAA001I The z/OS Log Forwarder started successfully
BPXM023I (GLALGF) GLAA002I The z/OS Log Forwarder initialization is complete

Cause

The user ID that is associated with the z/OS Log Forwarder start procedure has insufficient authority.

If the appropriate authority is granted to the z/OS Log Forwarder start procedure, the BPX messages do not precede the GLA messages.

Because the BPX messages precede the GLA messages, the z/OS SYSLOG Insight Pack does not recognize the GLA messages.

Solution

If you are using the Resource Access Control Facility (RACF®) as your System Authorization Facility (SAF) product, for example, complete the following steps to resolve this problem:

In RACF, add the BPX.CONSOLE resource to the class FACILITY by using the General Resource Profiles option in the RACF Services Option Menu.
In the BPX.CONSOLE profile that was created (or updated) in the preceding step, add the user ID that the z/OS Log Forwarder start procedure is associated with, and assign READ access to the user ID.
Issue the following command to activate your changes:
```
SETROPTS RACLIST(FACILITY) REFRESH
```

After the changes are made in RACF, the z/OS SYSLOG includes the following messages when the z/OS Log Forwarder starts:

S GLAPROC
GLAA001I The z/OS Log Forwarder started successfully
GLAA002I The z/OS Log Forwarder initialization is complete