AionDS Messages and Codes Guide
AionDS Messages and Codes Guide AionDS Messages and Codes Guide
IMS and TSO transaction driver messages .........................................................................................................................................................................................................˝.......................................... 16 2-18 AionDS Messages and Codes Not enough storage to allocate I/O area for message The IMS and TSO transaction drivers buffer the entire message from MAES or SAES. If the original buffer is too small and not enough memory exists to allocate a new buffer, then the message is not transmitted and the AionDS transaction driver issues this error. If this error occurs, increase the region size of the of the MPR or TSO address space where the AionDS transaction driver resides. .........................................................................................................................................................................................................˝.......................................... 20 VTAM session is inactive The VTAM session to MAES was not active when AionDS tried to receive or send a message to MAES. Either the session was not properly opened through the program IAESSTIN or the session has been terminated. .........................................................................................................................................................................................................˝.......................................... 24 Negative length specified on a SEND The maximum length for any single message is 32,767 bytes. The AESMLEN field contains a value that is greater than the maximum, which appears as a negative number to the transaction. .........................................................................................................................................................................................................˝.......................................... 28 Data request error If you receive this error, report it to PLATINUM Technical Support for AionDS. .........................................................................................................................................................................................................˝.......................................... 32 LU name was all blanks for an ACB OPEN The VTAM logical unit name of the AionDS transaction driver consisted of all blanks when IAESSTIN was called. This message indicates a problem with the IAESLUNM list of logical units.
IMS and TSO transaction driver messages .........................................................................................................................................................................................................˝.......................................... 36 The VTAM ACB on node xxxxxxx failed to OPEN properly (rr/cc) An error occurred trying to open the VTAM ACB on MAES node xxxxxxxx. The message includes the OPEN return code in register 15 (rr) as well as the ACB error code (cc). For more information: Refer to the IBM VTAM Programming manual for more information on the codes. .........................................................................................................................................................................................................˝.......................................... 36 The VTAM ACB failed to open properly (88/0) 1 When the system programmer defined the transaction in the IMS generation, the transaction could have been made eligible for processing in two message process regions at the same time. Under normal circumstances, the transaction can only be processed by a single message processing region at any one time. The AionDS/IMS transaction driver uses the transaction name as the node name when opening the VTAM ACB. If two message regions try to process transactions from the same queue, the first one gets use of the node name and the second one fails and writes this error message. 2 The message processing region can terminate without closing the ACB. Typically, this error is the result of an error with the transaction driver. The message processing region is left in a state where the ACB is still open and associated with that message processing region. The node name cannot be used in other regions or in that same message processing region. To alleviate this problem, you can stop the message processing region and then restart it. You can vary the VTAM node OFFLINE and then vary it back ONLINE from the VTAM operator’s console. .........................................................................................................................................................................................................˝.......................................... 36 The VTAM ACB failed to open properly (90/0) This error can be caused by running a consultation under IMS where the IMS transaction code has not been established as a VTAM node name. The AionDS/IMS transaction driver uses the transaction code as the application name in the VTAM ACB. Transaction Driver Messages 2-19
- 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 and 224: CICS transaction driver messages ..
- Page 225 and 226: CICS transaction driver messages No
- 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: 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
- Page 275 and 276: continued Return code Description 1
- Page 277 and 278: Status Codes MAES-specific codes ..
- Page 279 and 280: Chapter 6 MAESLOG Messages ........
- Page 281 and 282: MAESLOG messages The following list
- Page 283 and 284: MAESLOG messages ..................
IMS <strong>and</strong> TSO transaction driver messages<br />
.........................................................................................................................................................................................................˝..........................................<br />
16<br />
2-18 <strong>AionDS</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong><br />
Not enough storage to allocate I/O area for message<br />
The IMS <strong>and</strong> TSO transaction drivers buffer the entire message from MAES<br />
or SAES. If the original buffer is too small <strong>and</strong> not enough memory exists to<br />
allocate a new buffer, then the message is not transmitted <strong>and</strong> the <strong>AionDS</strong><br />
transaction driver issues this error. If this error occurs, increase the region<br />
size of the of the MPR or TSO address space where the <strong>AionDS</strong> transaction<br />
driver resides.<br />
.........................................................................................................................................................................................................˝..........................................<br />
20<br />
VTAM session is inactive<br />
The VTAM session to MAES was not active when <strong>AionDS</strong> tried to receive or<br />
send a message to MAES. Either the session was not properly opened<br />
through the program IAESSTIN or the session has been terminated.<br />
.........................................................................................................................................................................................................˝..........................................<br />
24<br />
Negative length specified on a SEND<br />
The maximum length for any single message is 32,767 bytes. The<br />
AESMLEN field contains a value that is greater than the maximum, which<br />
appears as a negative number to the transaction.<br />
.........................................................................................................................................................................................................˝..........................................<br />
28<br />
Data request error<br />
If you receive this error, report it to PLATINUM Technical Support for<br />
<strong>AionDS</strong>.<br />
.........................................................................................................................................................................................................˝..........................................<br />
32<br />
LU name was all blanks for an ACB OPEN<br />
The VTAM logical unit name of the <strong>AionDS</strong> transaction driver consisted of<br />
all blanks when IAESSTIN was called. This message indicates a problem<br />
with the IAESLUNM list of logical units.