AionDS Messages and Codes Guide
AionDS Messages and Codes Guide AionDS Messages and Codes Guide
CICS transaction driver messages .........................................................................................................................................................................................................˝.......................................... xxxx - TD ERROR (6007) 2-8 AionDS Messages and Codes UNABLE TO RECEIVE TERMINAL DATA. CONSULTATION ABORTED The transaction driver attempted a CICS RECEIVE on the user’s terminal, but the RECEIVE failed. Your CICS systems programmer should use the CICS log to determine the error and make the necessary corrections. .........................................................................................................................................................................................................˝.......................................... xxxx - MAES ERROR (6008) NO SESSIONS AVAILABLE TO MAKE A CICS CONNECTION TO nnnn The transaction driver tried to allocate a session to nnnn but found that no sessions were available. For maximum efficiency, you should have enough LU6.2 sessions allocated to CICS (connecting to nnnn) to satisfy the maximum number of concurrent users. .........................................................................................................................................................................................................˝.......................................... xxxx - MAES ERROR (6009) NODE nnnn HAS DIED. UNABLE TO RESUME YOUR CONSULTATION The MAES node nnnn is no longer active. Your consultation cannot continue. This error is caused by too many users on node nnnn. If this error persists after restarting the consultation, try increasing the value of MAXSESS in the DFHTCT. The syntax for MAXSESS is: where MAXSESS=(N,Q) N maximum number of sessions in the group Q maximum number of sessions that are to be supported as contention winners. The value specified for Q must not be greater than the number specified for N.
CICS transaction driver messages Note: The failed node may show active in CICS and VTAM. For more information: See Chapter 2 of the CICS Installation and Operation Guide for more information. .........................................................................................................................................................................................................˝.......................................... xxxx - TD ERROR (6010) A CICS ABEND HAS OCCURRED AT LABEL llllllll, ABEND CODE aaaa If the abend cannot be resolved by your CICS systems programmer, contact PLATINUM Technical Support for AionDS. .........................................................................................................................................................................................................˝.......................................... xxxx - TD ERROR (6011) VALUE FOR “:MAES=” IS GREATER THAN 4 BYTES The target MAES node name is limited to 4 bytes. .........................................................................................................................................................................................................˝.......................................... xxxx - TD ERROR (6012) nnnn IS AN INVALID PDB TYPE A type of parameter descriptor block contained in the fixed parameter list passed to the transaction driver is invalid. Correct the PDB structure and rerun the application. .........................................................................................................................................................................................................˝.......................................... xxxx - TD ERROR (6013) PDB COUNT INCONSISTENT WITH NUMBER OF PARMS PASSED The size of the PDB defines the number of parameters represented. The size of the PDB is larger than the number of valid parameters. .........................................................................................................................................................................................................˝.......................................... xxxx - TD ERROR (6014) NO KNOWLEDGE BASE NAME LENGTH SPECIFIED IN PDB The size of the knowledge base name parameter was zero. Transaction Driver Messages 2-9
- Page 173 and 174: AionDS runtime errors .............
- Page 175 and 176: AionDS runtime errors .............
- Page 177 and 178: AionDS runtime errors .............
- Page 179 and 180: AionDS runtime errors .............
- Page 181 and 182: AionDS runtime errors .............
- Page 183 and 184: AionDS runtime errors .............
- Page 185 and 186: AionDS runtime errors .............
- Page 187 and 188: AionDS runtime errors .............
- Page 189 and 190: AionDS runtime errors .............
- Page 191 and 192: AionDS runtime errors .............
- Page 193 and 194: AionDS runtime errors .............
- Page 195 and 196: AionDS runtime errors .............
- Page 197 and 198: AionDS runtime errors .............
- Page 199 and 200: AionDS runtime errors .............
- Page 201 and 202: AionDS runtime errors .............
- Page 203 and 204: AionDS runtime errors .............
- Page 205 and 206: AionDS runtime errors .............
- Page 207 and 208: AionDS runtime errors .............
- Page 209 and 210: AionDS runtime errors .............
- Page 211 and 212: AionDS runtime errors .............
- Page 213 and 214: AionDS runtime errors .............
- Page 215 and 216: AionDS runtime errors .............
- Page 217 and 218: Chapter 2 Transaction Driver Messag
- Page 219 and 220: Post Version 6.00-style messages (M
- Page 221 and 222: CICS transaction driver messages ..
- Page 223: CICS transaction driver messages ..
- Page 227 and 228: Version 6.0-style messages (MSG600=
- Page 229 and 230: CICS transaction driver messages ..
- Page 231 and 232: CICS transaction driver messages ..
- Page 233 and 234: IMS and TSO transaction driver mess
- Page 235 and 236: IMS and TSO transaction driver mess
- Page 237 and 238: IMS and TSO transaction driver mess
- Page 239 and 240: IMS and TSO transaction driver mess
- Page 241 and 242: IMS and TSO transaction driver mess
- Page 243 and 244: IMS and TSO transaction driver mess
- Page 245 and 246: IMS and TSO transaction driver mess
- Page 247 and 248: Chapter 3 CICS/VS Exception Conditi
- Page 249 and 250: CICS/VS exception conditions ......
- Page 251 and 252: CICS/VS exception conditions ......
- Page 253 and 254: CICS/VS exception conditions ......
- Page 255 and 256: CICS/VS exception conditions ......
- Page 257 and 258: CICS/VS exception conditions ......
- Page 259 and 260: CICS/VS exception conditions ......
- Page 261 and 262: Chapter 4 DB/DC Program Interface R
- Page 263 and 264: ADSMSW (Message switching function)
- Page 265 and 266: ADSULINK (User link facility) .....
- Page 267 and 268: ADSPSB (Schedule a new PSB - AionDS
- Page 269 and 270: Chapter 5 MAES Error Codes ........
- Page 271 and 272: Code number Description 202 3270 Da
- Page 273 and 274: continued Return Code Description 3
CICS transaction driver messages<br />
.........................................................................................................................................................................................................˝..........................................<br />
xxxx - TD ERROR<br />
(6007)<br />
2-8 <strong>AionDS</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong><br />
UNABLE TO RECEIVE TERMINAL DATA. CONSULTATION<br />
ABORTED<br />
The transaction driver attempted a CICS RECEIVE on the user’s terminal,<br />
but the RECEIVE failed. Your CICS systems programmer should use the<br />
CICS log to determine the error <strong>and</strong> make the necessary corrections.<br />
.........................................................................................................................................................................................................˝..........................................<br />
xxxx - MAES ERROR<br />
(6008)<br />
NO SESSIONS AVAILABLE TO MAKE A CICS CONNECTION TO<br />
nnnn<br />
The transaction driver tried to allocate a session to nnnn but found that no<br />
sessions were available. For maximum efficiency, you should have enough<br />
LU6.2 sessions allocated to CICS (connecting to nnnn) to satisfy the<br />
maximum number of concurrent users.<br />
.........................................................................................................................................................................................................˝..........................................<br />
xxxx - MAES ERROR<br />
(6009)<br />
NODE nnnn HAS DIED. UNABLE TO RESUME YOUR<br />
CONSULTATION<br />
The MAES node nnnn is no longer active. Your consultation cannot<br />
continue. This error is caused by too many users on node nnnn. If this error<br />
persists after restarting the consultation, try increasing the value of MAXSESS<br />
in the DFHTCT.<br />
The syntax for MAXSESS is:<br />
where<br />
MAXSESS=(N,Q)<br />
N maximum number of sessions in the group<br />
Q maximum number of sessions that are to be supported as contention<br />
winners. The value specified for Q must not be greater than the<br />
number specified for N.
Change language