Invalid FM header: The FM header was not understood or
translatable by the receiver, or an FM header was expected but not
present. For LU 6.2, this sense code is sent in FMH-7 or UNBIND.
Table 1 shows the usage of
the allowed values by LU type.
Table 1. Usage of hexadecimal
1008 sense code specific information by LU type| Range |
LU 1 |
LU 4 |
LU 6.1 |
LU 6.2 |
|---|
| 0801–0824 |
X |
X |
|
|
| 0825 |
X |
|
|
|
| 0826–082A |
X |
X |
|
|
| 2001–200D |
X |
X |
|
|
| 200E |
X |
X |
X |
|
| 200F–201C |
X |
X |
|
|
| 201D |
|
|
|
X |
| 4001–400E |
X |
X |
|
|
| 6000 |
|
|
|
X |
| 6001,6004 |
|
|
X |
|
| 6005 |
|
|
X |
X |
| 6006–6008 |
|
|
X |
|
| 6009 |
|
|
X |
X |
| 600A |
|
|
X |
|
| 600B |
|
|
X |
X |
| 600C–6010 |
|
|
X |
|
| 6011–6034 |
|
|
|
X |
| 6040 |
|
|
X |
X |
| 6041 |
|
|
|
X |
| 6046 |
|
|
|
X |
| 6047 |
|
|
|
X |
| 6048 |
|
|
|
X |
| C000–C003 |
|
|
X |
|
Bytes 2 and 3 following the sense code contain sense code
specific information.
- 0000
- No specific code applies.
- 0801
- The function code parameters are not valid.
- 0803
- The forms functions cannot be performed.
- 0805
- The copy function cannot be performed.
- 0806
- Compaction table outside the supported set: The number of master
characters is not within the valid range.
- 0807
- The PDIR (peripheral data information record) identifier is not
valid.
- 0808
- The printer train function cannot be performed.
- 0809
- The FCB (forms control block) load function cannot be performed.
- 080A
- The FCB (forms control block) load function is not supported.
- 080B
- The compaction table name is not valid.
- 080C
- The ACCESS is not valid.
- 080D
- The RECLEN is not valid.
- 080E
- The NUMRECS is not valid.
- 080F
- The data set is in use.
- 0810
- The data set cannot be found.
- 0811
- The password is not valid.
- 0812
- The function is not allowed for the destination or for the data
set.
- 0813
- The record is too long.
- 0814
- The data set is full.
- 0815
- The RECID is not valid.
- 0817
- The VOLID format is not valid.
- 0818
- The maximum number of logical records per chain is exceeded.
- 0819
- The data set exists.
- 081A
- No space is available.
- 081B
- The VOLID is not valid.
- 081C
- The DSACCESS is not valid.
- 081D
- The RECTYPE is not valid or the data set cannot be found.
- 081E
- The resolution space is insufficient.
- 081F
- The key technique is not valid.
- 0820
- The key displacement is not valid.
- 0821
- The key is not valid.
- 0822
- There is an not valid N (number of records).
- 0823
- The KEYIND is not valid.
- 0824
- The SERID is not valid.
- 0825
- Disk error: An error was detected while reading from, or writing
on, the disk.
- 0826
- The RECID format is not valid.
- 0827
- The password has not been supplied.
- 0828
- The record ID has not been supplied.
- 0829
- The volume ID has not been supplied.
- 082A
- The PGMNAME is not valid.
- 2001
- The destination (active) is not valid.
- 2002
- The destination (inactive) is not valid.
- 2003
- The destination (suspended) is not valid.
- 2004
- The suspend-resume sequence is not valid.
- 2005
- There has been an interruption level violation.
- 2006
- The resume properties are not valid.
- 2007
- The destination is not available.
- 2008
- The end sequence is not valid.
- 2009
- The FM header length is not valid.
- 200A
- Field setting is not valid: The reserved field is set to one
or the setting is not defined.
- 200B
- Destination is not valid: The destination does not exist.
- 200C
- The ERCL is not valid.
- 200D
- The data stream profile (DST) is not valid.
- 200E
- Concatenation indicator is not valid: The concatenation indicator
is on, but concatenation is not allowed.
- 200F
- FM data is not allowed for the header.
- 2010
- The FM header set specified in the BIND has been violated.
- 2014
- The FM header was not sent concatenated.
- 2019
- The stack reference indicator (SRI) is not valid.
- 201A
- The CMI modification could not be accepted.
- 201B
- The CPI modification could not be accepted.
- 201C
- The ECRL modification could not be accepted.
- 201D
- FM header and associated data mismatch: The FM header indicated
that associated data would or would not follow (for example, FM Header
7 followed by log data, or FM Header 5 followed by program-initialization
parameters), but this indication was in error; or a previously received
RU [for example, -RSP(X'0846')] implied that an FM header
would follow, but none was received.
- 4001
- FM header type for this LU is not valid: The type of the FM header
is other than five, seven, or 12.
- 4002
- The FMH code is not valid.
- 4003
- Compression is not supported.
- 4004
- Compaction is not supported.
- 4005
- Basic exchange is not supported.
- 4006
- Only basic exchange is supported.
- 4007
- The medium is not supported.
- 4008
- There has been a code selection compression violation.
- 4009
- FMHC is not supported.
- 400A
- Demand select is not supported.
- 400B
- DSNAME is not supported.
- 400C
- The media subaddress field is not valid.
- 400D
- There are insufficient resources to perform the requested function.
- 400E
- Data stream profile (DSP) select is not supported.
- 6000
- FM header length not correct: The value in the FM header length
field differs from the sum of the lengths of the subfields of the
FM header.
- 6001
- The deblocking algorithm (DBA) is not valid.
- 6004
- The queue name length is not valid.
- 6005
- Access security information length field not correct: The value
in the access security information length field differs from the sum
of the lengths of the access security information subfields.
- 6006
- The data stream profile (DSP) is not valid.
- 6007
- The FMH-7 is not preceded by a negative response carrying sense
code X'0846'.
- 6008
- The attach access code is not valid.
- 6009
- Parameter length is not valid: The field that specifies the length
of fixed-length parameters has a setting that is not valid.
- 600A
- This is not the first FMH-5, the interchange unit type is not
the same as the old, and the interchange unit end indicator is off.
- 600B
- Unrecognized FM header command code: The partner LU received an
FM header command code that it does not recognize. For LU 6.2, this
sense data is sent only in FMH-7.
- 600C
- A null sequence field is required.
- 600D
- User-to-user program transition is not allowed.
- 600E
- User to non-SNA defined program transition is not allowed.
- 600F
- The FMH-5 reset attached program (RAP) was not sent properly.
- 6010
- The FMH-5 reset attached program (RAP) was sent with an inactive
attach register.
- 6011
- Logical unit of work (LUW) not valid: The LUW length field (in
a compare states GDS variable or an FMH-5) is incorrect, or the length
field is not valid, or a LUW ID is not present but is required by
the setting of the synchronization level field.
- 6021
- Transaction program name not recognized: The FMH-5 attach command
specifies a transaction program name that the receiver does not recognize.
This sense data is sent only in FMH-7.
- 6031
- PIP not allowed: The FMH-5 attach command specifies that program
initialization parameter (PIP) data is present, but the receiver does
not support PIP data for the specified transaction program. This sense
data is sent only in FMH-7.
- 6032
- PIP not specified correctly: The FMH-5 attach command specifies
a transaction program name that requires program initialization parameter
(PIP) data, and either the FMH-5 specifies PIP data is not present
or the number of PIP subfields present does not agree with the number
required for the program. This sense data is sent only in FMH-7.
- 6034
- Conversation type mismatch: The FMH-5 attach command specifies
a conversation type that the receiver does not support for the specified
transaction program. This sense data is sent only in FMH-7.
- 6040
- Attach parameter is not valid: A parameter in the FMH-5 attach
command conflicts with the statement of LU capability previously provided
in the BIND negotiation.
- 6041
- Synchronization level not supported: The FMH-5 attach command
specifies a synchronization level that the receiver does not support
for the specified transaction program. This sense data is sent only
in FMH-7.
- 6042
- Reconnection not supported: The FMH-5 attach command specifies
reconnection support, but the receiver does not support reconnection
for the specified transaction program. This sense data is sent only
in FMH-7.
- 6043
- Unable to reconnect transaction program—no retry: The FMH-5
reconnect command specifies the conversation correlator of a transaction
program to which the receiver cannot reconnect. The condition is
not temporary. This sense data is sent only in FMH-7.
- 6044
- Unable to reconnect transaction program—retry allowed: The
FMH-5 reconnect command specifies the conversation correlator of a
transaction program to which the receiver cannot reconnect. The condition
is temporary. This sense data is sent only in FMH-7.
- 6046
- An SNA/DS transaction program is unable to allocate a conversation
with an SNA/DS partner.
- 6047
- An SNA/DS transaction program in conversation with an adjacent
SNA/DS transaction program has detected from LU 6.2 PS a return code
of resource_failure.
- 6048
- An SNA/DS transaction program in conversation with an adjacent
SNA/DS transaction program has detected from LU 6.2 PS a return code
of deallocate type (abend).
- 6050
- For the receiver, one of the following conditions exists:
- Extended security bit is on and GDS variable X'12F6' does
not immediately follow the attach FMH-5 and PIP data.
- Extended security bit is off and GDS variable X'12F6' follows
the attach FMH-5.
For the sender, one of the following conditions exist: - The partner responded to the attach with any data other than an
FMH7 or an authenticator reply (GDS id X'12F8').
- The authenticator reply subfield (X'FF85') is absent.
- A subfield occurs more than once.
- 6051
- One of the following conditions exist:
- The length of the GDS variable is incorrect. The length must be
greater than zero and must equal to (length_field_value -2).
- An unidentified subfield is present in the GDS variable.
- The total length of a subfield is not equal to the value in its
length field minus 2.
- 6053
- The length of the GDS variable is incorrect. It is the responsibility
of the application to ensure that the GDS variable length is correct.
For the sender, the length must be greater than or equal to two and
must equal the value in the length field.
- 6054
- For the receiver, the extended security bit is on and either old
FMH-5 security bits are on or the old access security information
fields are present. For the sender, the authenticator reply fails
the checks applied by the security manager. (Purge ID from Signed
On To list.)
- 6056
- The partner responded to the attach with any data other than an
FMH7 or an authentication token (GDS variable X'12F6').
- 6057
- The authentication token GDS requested that additional token exchanges
be handled via the distributed authentication service TP. However,
the FMH5 did not contain a valid conversation correlator.
- C000
- The header is not supported.
- C001
- The header length is not valid.
- C002
- There has been a logical message services block-level error.
- C003
- There is a version ID mismatch.