z/OS MVS System Codes
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


DFB

z/OS MVS System Codes
SA38-0665-00

DFB

Explanation

During processing in a functional subsystem (FSS) address space, a JES3 module detected an error. A hexadecimal reason code in register 15 and/or the SDWA explains the error. (Note: when the reason code is X'26', it will appear only in the SDWA, not in register 15.)

When the reason code is X'65', X'66', X'67', or X'68' then the error indicates the JES3 TCP/IP NJE server exits module detected a datastream error and could not continue.
Code
Explanation
01
The connect subsystem interface (SSI) routine in module IATSICD determined that the START command for the FSS address space did not contain a token.
02
The connect subsystem interface (SSI) routine in module IATSICD could not locate the MEMDATA header for the FSS address space.
03
The connect subsystem interface (SSI) routine in module IATSICD could not establish the listen task, IATFCLT, for the FSS or the FSA.
05
Module IATSICD encountered an error during JESXCF attach processing (IXZXIXAT service).
06
Module IATSICD encountered an error during JESXCF mailbox build processing (IXZXIXMB service) for the default mailbox.
07
Module IATSICD encountered an error during JESXCF mailbox delete processing (IXZXIXMD service) for the default mailbox.
08
Module IATSICD encountered an error during JESXCF detach processing (IXZXIXDT service).
0B
The common end-of-task exit routine in module IATSICD found that a task in the FSS address space had ended unexpectedly.
0C
The common end-of-task exit routine in module IATSICD could not identify a task that had ended.
15
The writer FSA specific connect routine, IATFPCC, could not initialize for GETDS spool access using the block spooler.
16
The writer FSA specific connect routine, IATFPCC, could not establish the read-ahead task for the FSA.
17
The writer FSA specific connect routine, IATFPCC, could not establish the checkpoint writer task for the FSA.
1F
The FSI order interface routine, IATFCOR, received a nonzero return code from the FSS or FSA order routine.
20
The FSI post interface routine, IATFCPT, received a nonzero return code from the FSA post routine.
21
Module IATFCLT encountered an error during JESXCF mailbox build processing (IXZXIXMB Service) for a FSS/FSA mailbox.
22
Module IATFCLT encountered an error during JESXCF mailbox clear processing (IXZXIXMC Service) for a FSS/FSA mailbox.
23
Module IATFCLT encountered an error during JESXCF receive message processing (IXZXIXRM Service) for a FSS/FSA mailbox.
24
Module IATFCLT encountered an error during JESXCF acknowledge message processing (IXZXIXAC Service) for a FSS/FSA mailbox.
25
Module IATFCLT encountered an error during JESXCF mailbox delete processing (IXZXIXMD) for a FSS/FSA mailbox.
26
A stop FSA abnormal order has been received from JES3. If a dump has been requested, a dump will be taken as part of abend processing of the FSA task.
29
The C/I FSS order processing routine, IATIIFO, found that the FSI parameter list did not contain an order.
2A
The C/I FSS order processing routine, IATIIFO, received an incorrect order type.
2B
The C/I FSS order processing routine, IATIIFO, received an incorrect stop FSS order.
2C
The C/I FSS order processing routine, IATIIFO, could not locate the C/I communications block (CCB).
33
The writer FSA quick-cell service routine, IATFPQC, failed to get an index, because the first free index was incorrect.
34
The writer FSA quick-cell service routine, IATFPQC, failed to get a buffer, because the first free buffer was incorrect.
35
The writer FSA quick-cell service routine, IATFPQC, failed to free an index, because the index passed in the request was incorrect.
36
The writer FSA quick-cell service routine, IATFPQC, failed to free a buffer, because the buffer passed in the request was incorrect.
3D
While reading a data set checkpoint record, the writer FSA GETDS routine, IATFPGD, received an error return from the block spooler routine; the error return indicated that the parameter list was incorrect.
3E
While reading a data set checkpoint record, the writer FSA GETDS routine, IATFPGD, received an error return from the block spooler routine; the error return indicated that the spool address was incorrect.
3F
While reading a data set checkpoint record, the writer FSA GETDS routine, IATFPGD, received an error return from the block spooler routine; the error return indicated that an error occurred during a cross-address space move.
47
While reading the scheduler work block (SWB), the writer FSA SWB processing service routine, IATFPSB, received an error return from the block spooler routine; the error return indicated that the parameter list was incorrect.
48
While reading the scheduler work block (SWB), the writer FSA SWB processing service routine, IATFPSB, received an error return from the block spooler routine; the error return indicated that the spool address was incorrect.
49
While reading the scheduler work block (SWB), the writer FSA SWB processing service routine, IATFPSB, received an error return from the block spooler routine; the error return indicated that an error occurred during a cross-address space move.
4A
The scheduler JCL facility (SJF) PUTSWB function returned an error code to the writer FSA scheduler work block (SWB) processing service routine, IATFPSB.
4B
The scheduler JCL facility (SJF) UPDATE function returned an error code to the writer FSA scheduler work block (SWB) processing service routine, IATFPSB.
4C
The scheduler JCL facility (SJF) DELETESWB function returned an error code to the writer FSA scheduler work block (SWB) processing service routine, IATFPSB.
51
The writer FSA read-ahead task, IATFPRA, could not initialize for spool access using the block spooler.
52
While reading data from spool, the writer FSA read-ahead task, IATFPRA, received an error return from the block spooler routine; the error return indicated that the parameter list was incorrect.
53
While reading data from spool, the writer FSA read-ahead task, IATFPRA, received an error return from the block spooler routine; the error return indicated that the spool address was incorrect.
54
While reading data from spool, the writer FSA read-ahead task, IATFPRA, received an error return from the block spooler routine; the error return indicated that an error occurred during a cross-address space move.
55
The writer FSA read-ahead task, IATFPRA, found an error in the format of a spool data buffer.
56
The writer FSA read-ahead task, IATFPRA, found an error in the format of a JESNEWS data buffer.
5B
The writer FSA checkpoint writer task, IATFPCW, could not initialize for spool access using the block spooler.
5C
While writing a data set checkpoint record, the writer FSA checkpoint writer task, IATFPCW, received an error return from the block spooler routine; the error return indicated that the parameter list was incorrect.
5D
While writing a data set checkpoint record, the writer FSA checkpoint writer task, IATFPCW, received an error return from the block spooler routine; the error return indicated that the spool address was incorrect.
5E
While writing a data set checkpoint record, the writer FSA checkpoint writer task, IATFPCW, received an error return from the block spooler routine; the error return indicated that an error occurred during a cross-address space move.
65
The Netserv exit subtask detected data stream corruption in the inbound SYSIN record. The subtask is terminated.
66
The Netserv exit subtask detected data stream corruption in the inbound SYSOUT record. The subtask is terminated.
67
The Netserv exit subtask detected data stream corruption in the outbound SYSIN record. The subtask is terminated.
68
The Netserv exit subtask detected data stream corruption in the outbound SYSOUT record. The subtask is terminated.

System action

The system abnormally ends the task.

Most failures in the read-ahead task, IATFPRA, and in the checkpoint writer task, IATFPCW, cause processing of the current data set to be ended. The task is reinstated to resume processing with the next data set.

All other failures result in the FSA or of the entire FSS address space ending.

Operator response

Notify the system programmer. If the FSS address space was ended and if this is not a recurring error, issue the appropriate command to restart the FSS.

System programmer response

Format the SVC dump with the interactive problem control system (IPCS).

If the problem occurs in JES3, save the hardcopy log.

Source

JES3

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014