DC7

Explanation
While running the APPC/MVS transaction scheduler,
the system found an unrecoverable error.
A reason code further
describes the error: Code
Explanation
01
A CLASSADD statement in parmlib tried to modify the characteristics
of a class that already existed.
03
The system found an incorrect transaction scheduling type for
a transaction program (TP).
04
The system could not run the Resource Access Control Facility
(RACF®).
05
The system could not create a security environment.
07
The system could not delete the security environment.
08
The system could not obtain SYSOUT and accounting information
from RACF.
10
The GETTRANS service could not notify system management of a new
TP.
11-20
An internal error occurred.
21, 22, 23
The system could not initialize the APPC/MVS transaction scheduler.
24, 25
The system could not create a new ASCH initiator.
28-32
An internal error occurred.
33
The system could not obtain a transaction from APPC.
34
The system could not initialize the APPC/MVS transaction scheduler.
35
An attempt was made to start the ASCH address space by something
other than a START command.
36
The system could not initialize the ASCH.
37
An internal error occurred.
38-41
The system could not create a new ASCH initiator.
42, 43
While APPC was active, the system could not initialize ASCH.
44
The system could not verify the subsystem specified on the SUBSYS
keyword in the current parmlib configuration.
45
While the system was processing a DISPLAY ASCH command, an error
occurred.
46
When the system tried to invoke the APPC associate service, an
error occurred.
47
The system could not verify the subsystem specified on the SUBSYS
keyword in the current parmlib configuration.
48, 49, 50
After being notified that APPC was active, the system could not
initialize the APPC/MVS transaction scheduler.
51
The ASCH failed while it was ending.
52, 53, 54
The system could not initialize the APPC/MVS transaction scheduler.
56
After being notified that APPC was active, the system could not
initialize the APPC/MVS transaction scheduler.
57
The system could not initialize the APPC/MVS transaction scheduler.
59-65
An internal error occurred.

System action
Depending on the reason code, one of following: Code
System Action
01
The system does not process the incorrect CLASSADD statement.
 Other processing continues.
03
The APPC scheduler does not schedule the TP. The initiator address
space where the TP should have run ends. The requestor of the TP receives
a return code indicating that the conversation was deallocated.
04-07
Unpredictable.
08
The initiator address space where the TP was scheduled to run
ends.  The requestor of the TP receives a return code indicating that
the conversation was deallocated.
10
If the TP provided recovery, recovery receives control. Otherwise,
the TP ends.
11-20
Unpredictable.
21-23
The APPC/MVS transaction scheduler ends. No restart is possible.
24-25
The system continues processing with the existing initiator.
26-27
The system continues processing.  If this error occurs again in
a certain time period, the system attempts an automatic restart. 
If restart is unsuccessful, the APPC/MVS transaction scheduler ends.
28-32
Unpredictable.
33
The system continues processing.  If this error occurs again in
a certain time period, the system attempts an automatic restart. 
If restart is unsuccessful, the APPC/MVS transaction scheduler ends.
34
The APPC/MVS transaction scheduler ends.  No restart is possible.
35
The system does not initialize the ASCH address space.
36-37
The APPC/MVS transaction scheduler ends.  No restart is possible.
38-41
The system continues processing with the existing initiator.
42-43
The system automatically attempts a restart.  If this error occurs
again, the APPC/MVS transaction scheduler ends.
44
The system continues processing with the existing initiator.
45
The system rejects the DISPLAY ASCH command.
46
The system continues processing. The requestor of the transaction
receives a return code indicating that the conversation was deallocated.
47
The system continues processing with the existing initiator.
48-50
The system automatically attempts a restart.  If this error occurs
again, the APPC/MVS transaction scheduler ends.
51-55
The APPC/MVS transaction scheduler ends. No restart is possible.
56
The system automatically attempts a restart.  If this error occurs
again, the APPC/MVS transaction scheduler ends.
57
The APPC/MVS transaction scheduler ends. No restart is possible.
58-60
Unpredictable.
61, 62
The system continues processing.
63, 64
The system automatically attempts a restart.  If this error occurs
again, the APPC/MVS transaction scheduler ends.

Operator response
Depending on the reason code, do one of the
following: Code
Explanation
01, 03, 04
Enter a DISPLAY ASCH command to find the incorrect CLASSADD statement.
 Notify the system programmer.
08
Contact the RACF administrator
to check the installation's security package for information identifying
the error.
10-22
Notify the system programmer.
23
Enter a START ASCH command. If the error occurs again, notify
the system programmer.
24
Notify the system programmer.
25
If the APPC/MVS transaction scheduler is not processing critical
work, enter a CANCEL ASCH command to end the APPC/MVS transaction
scheduler. Then enter the START ASCH command to restart the APPC/MVS
transaction scheduler. Otherwise, notify the system programmer.
26
Notify the system programmer.
27
If the APPC/MVS transaction scheduler ends, notify the system
programmer.  Enter a START ASCH command.
28-32
Notify the system programmer.
33
The system continues processing.  The requestor of the transaction
receives a return code indicating the conversation was deallocated.
34
Enter a START ASCH command. If the error occurs again, notify
the system programmer.
35
Notify the system programmer.
36
If the APPC/MVS transaction scheduler ends, notify the system
programmer.  Enter a START ASCH command.
37
Enter a START ASCH command.  If the error occurs again, notify
the system programmer.
38, 39, 40
Notify the system programmer.
41
If the APPC/MVS transaction scheduler is not processing critical
work, enter a CANCEL ASCH command to end the APPC/MVS transaction
scheduler. Then enter the START ASCH command to restart the APPC/MVS
transaction scheduler. Otherwise, notify the system programmer.
42
Notify the system programmer.
43
If the APPC/MVS transaction scheduler ends, notify the system
programmer.  Enter a START ASCH command.
44
If the error occurs again, notify the system programmer.
45
Enter the DISPLAY ASCH command again. If the error occurs again,
notify the system programmer.
46
Notify the system programmer.
47
If the APPC/MVS transaction scheduler is not processing critical
work, enter a CANCEL ASCH command to end the APPC/MVS transaction
scheduler. Then enter the START ASCH command to restart the APPC/MVS
transaction scheduler. Otherwise, notify the system programmer.
48, 49
Notify the system programmer.
50
If the APPC/MVS transaction scheduler ends, notify the system
programmer.  Enter a START ASCH command.
51-54
Notify the system programmer.
55
If the APPC/MVS transaction scheduler ends, notify the system
programmer.  Enter a START ASCH command.
56
If the APPC/MVS transaction scheduler ends, enter a START ASCH
command. If the error occurs again, notify the system programmer.
57-61
Notify the system programmer.
62
If the APPC/MVS transaction scheduler is not processing critical
work, enter a CANCEL ASCH command to end the APPC/MVS transaction
scheduler. Then enter the START ASCH command to restart the APPC/MVS
transaction scheduler. Otherwise, notify the system programmer.
63, 64
If the error occurs again, notify the system programmer.

System programmer response
Depending on the reason code, do one
of the following: Code
Explanation
01
Delete the incorrect class using a CLASSDEL statement in the current
parmlib configuration. Then try to add the class again, using a CLASSADD
statement. If the error occurs again, search problem reporting databases
for a fix for the problem. If no fix exists, contact the IBM® Support Center.
03, 04
Search problem reporting data bases for a fix for the problem.
If no fix exists, contact the IBM Support
Center.
05
Check to see whether a program issued the z/OS® UNIX System
Services spawn callable service, passing a user ID that is not valid.
 If the user ID is valid, search problem reporting data bases for
a fix for the problem.  If no fix exists, contact the IBM Support Center.
07
Search problem reporting data bases for a fix for the problem.
 If no fix exists, contact the IBM Support
Center.
08
Contact the RACF administrator.
Check the installation's security package for information identifying
the error.
10-34
Search problem reporting data bases for a fix for the problem.
 If no fix exists, contact the IBM Support
Center.
35
Determine how APPC/MVS transaction scheduler initialization was
invoked and take appropriate actions to prevent re-occurrences.  The
only proper way to initialize the scheduler is with the START command.
36-43
Search problem reporting data bases for a fix for the problem.
 If no fix exists, contact the IBM Support
Center.
44
Enter a valid JES subsystem on the SUBSYS keyword in the current
parmlib configuration.
45-65
Search problem reporting data bases for a fix for the problem.
 If no fix exists, contact the IBM Support
Center.

Source
APPC/MVS transaction scheduler