Control vector error on a directory services GDS variable.
Bytes 2 and 3 following the sense code contain sense code
specific information.
- 003C
- Missing associated resource entry (X'3C') control vector on find
or found.
- 003D
- Missing directory entry (X'3D') control vector on find or found.
- 0060
- Missing CV60 on LOCATE GDS variable.
- 0080
- Control vector not valid.
- 023C
- Conflicting directory entry, or associated resource entry (X'3C')
control vector not valid.
- 502B
- No RSCV received from a network node server.
- 502C
- No COS/TPF control vector received in a CD-Initiate reply from
a network node server.
- 502D
- The COS/TPF control vector received on the BIND is different from
that on the corresponding Locate.
VTAM® hint: A dump should be taken for problem
determination.
- 5046
- TG vectors not present in a CD-Initiate from an end node OLU or
DLU.
VTAM hint: This
sense code can also be set by AS/400® when
an attempt to establish a session from one AS/400 to a second AS/400 across a VTAM network
fails. Sessions across three different networks using APPN links are
not supported in VTAM. See
the information about common APPN problems in the z/OS Communications Server: SNA Diagnosis Vol
1, Techniques and Procedures for more information about this problem.
- A080
- Missing command parameters (X'80') control vector on find.
- A082
- Missing search argument directory entry (X'82') control vector
on find.
- B280
- A found from an end node indicated the directory entry for a located
resource was a wild-card entry.