15F

Explanation
A SYSEVENT macro incorrectly invoked the system
resources manager (SRM). Register 15 contains a hexadecimal reason
code that explains the error: Code
Explanation
04
The address space identifier (ASID), the SYSEVENT code, or an
input parameter was incorrect.
08
Program was not authorized to issue the SYSEVENT.
0C
A page fault occurred when the system referred to a data area
assumed to be fixed.
10
A protection check occurred; the program issuing the macro did
not have the correct storage key for storing in the parameter data
area.
14
A program held the SRM lock before the SYSEVENT macro invoked
SRM.
18
The SRM recovery routine converts this reason code to completion
code X'25F'.
1C
A SYSEVENT TRANSWAP or REQSWAP with an event control block (ECB)
was issued when the maximum allowed number of pending TRANSWAPs or
REQSWAPs with ECBs had already been reached.
20
An SRM stack overflow was detected.
24
The SRM entry point did not receive an SRM recovery parameter
area (RRPA).
28
An unexpected condition occurred while enforcing a defined capacity
limit.One reason is that the partition weight is too high relative
to the defined capacity limit. As a result, the phantom weight SRM
tries to assign is not valid. If this is the case, check the phantom
weight assigned to the LPAR. The phantom weight is calculated based
on the defined LPAR capacity, the total CEC capacity and the partition
weight. The value specified for a phantom weight should not exceed
1000 times the number of active LPARs. For more information about
how to calculate the phantom weight, see Workload Management Participants, Workload Management
and Workload Licence Charges in z/OS MVS Planning: Workload Management.
If
the phantom weight is correct, search problem reporting databases
for a fix for the problem. If no fix exists, open a problem record
and provide the dump to the IBM® Support
Center for diagnosis. 

2C
The invocation of the SYSEVENT macro with ENTRY=UNAUTHPC failed.
See R0 for more information:xxxx0004
Sysevent is not enabled for ENTRY=UNAUTHPC.
xxxx0801
The caller is in SRM mode and Task mode is required.
xxxx0803
The caller must be enabled for interrupts.
xxxx0804
No locks must be held.
xxxx0823
The caller invoked service while DAT is set to OFF.
xxxx0824
The caller invoked service in AMODE24.
xxxx0841
The caller is in cross-memory (XMEM) mode.
xxxx08B6
The caller must not be authorized.

Other
Internal SRM error. Search problem reporting databases for a fix
for the problem. If no fix exists, save the dump and contact IBM support.

System action
Take action according to the different reason
codes.
For reason codes 04 to 24, and 2C: The system
abnormally ends the issuer of the SYSEVENT macro. The system writes
messages and a logrec data set error record.
For reason code
28: The system can no longer enforce a defined capacity limit.

System programmer response
Take action according to different
reason codes.
For reason codes 04 to 24, and 2C: If
an installation-provided program issued the SYSEVENT, ensure that
the program is authorized.  Correct the error indicated by the reason
code.  Run the job again. If an IBM-provided program issued the SYSEVENT,
run the job again.  In either case, if the error recurs, search problem
reporting data bases for a fix for the problem. If no fix exists,
contact the IBM Support Center.
Provide the logrec data set error record and the SYSOUT output for
the job.
For reason code 28: Increase the defined capacity limit,
or adjust the weight of the partition.

Source
System resources manager (SRM)