AionDS Messages and Codes Guide
AionDS Messages and Codes Guide AionDS Messages and Codes Guide
IMS and TSO transaction driver messages IMS and TSO transaction driver messages .........................................................................................................................................................................................................˝.......................................... Overview 2-16 AionDS Messages and Codes This section lists the messages that are issued by the AionDS/IMS transaction driver, the TSO transaction driver, or both. The message format is described as follows: where tt Error nnnn: text tt one of the following: MS for errors occurring with MAES IM for errors occurring with IMS LR for errors occurring with VTAM TY for miscellaneous errors occurring with the transaction driver nnnn error number text descriptive text explaining the error condition The IMS and TSO transaction driver messages are listed below in numeric order. The header (tt Error) has been omitted for brevity. .........................................................................................................................................................................................................˝.......................................... (No error number) Development session ended The AionDS/IMS transaction driver displays this message at the end of a development session. This is informational only. .........................................................................................................................................................................................................˝.......................................... (No error number) Consultation with xxxxxxxx ended The AionDS/IMS transaction driver displays this message at the end of consultation xxxxxxxx. This is informational only.
IMS and TSO transaction driver messages .........................................................................................................................................................................................................˝.......................................... (No error number) Execution of xxxxxxxx complete The optimized knowledge base xxxxxxxx has finished executing. This is informational only. .........................................................................................................................................................................................................˝.......................................... (No error number) Actions : nnn, seconds : ssss, average : aaaa where nnn indicates the total number of session terminal inputs ssss indicates the CPU time consumed by the transaction driver aaaa indicates the average CPU time consumed for each input The AionDS/IMS transaction driver displays this message at the end of each consultation or development session. This is informational only. .........................................................................................................................................................................................................˝.......................................... (No error number) Session run on node xxxxxxxx The consultation was executed on the MAES region whose VTAM node name is xxxxxxxx. This is informational only. .........................................................................................................................................................................................................˝.......................................... (No error number) Please press PA1 to continue When switching from the conversational transaction driver to a nonconversational transaction, IMS requires an intervening message. The transaction driver sends out this message, asking the user to press PA1 which will cause the first message from the target transaction to be displayed. .........................................................................................................................................................................................................˝.......................................... 12 Record from MAES is too large for the I/O area The message sent from MAES or SAES was larger than the user area provided. This error typically occurs when a user-written program attempts to drive the link and the AESIOLEN field is not set properly. Transaction Driver Messages 2-17
- 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 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: CICS transaction driver messages ..
- 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
- 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
IMS <strong>and</strong> TSO transaction driver messages<br />
.........................................................................................................................................................................................................˝..........................................<br />
(No error number)<br />
Execution of xxxxxxxx complete<br />
The optimized knowledge base xxxxxxxx has finished executing. This is<br />
informational only.<br />
.........................................................................................................................................................................................................˝..........................................<br />
(No error number)<br />
Actions : nnn, seconds : ssss, average : aaaa<br />
where<br />
nnn indicates the total number of session terminal inputs<br />
ssss indicates the CPU time consumed by the transaction driver<br />
aaaa indicates the average CPU time consumed for each input<br />
The <strong>AionDS</strong>/IMS transaction driver displays this message at the end of each<br />
consultation or development session. This is informational only.<br />
.........................................................................................................................................................................................................˝..........................................<br />
(No error number)<br />
Session run on node xxxxxxxx<br />
The consultation was executed on the MAES region whose VTAM node<br />
name is xxxxxxxx. This is informational only.<br />
.........................................................................................................................................................................................................˝..........................................<br />
(No error number)<br />
Please press PA1 to continue<br />
When switching from the conversational transaction driver to a nonconversational<br />
transaction, IMS requires an intervening message. The<br />
transaction driver sends out this message, asking the user to press PA1 which<br />
will cause the first message from the target transaction to be displayed.<br />
.........................................................................................................................................................................................................˝..........................................<br />
12<br />
Record from MAES is too large for the I/O area<br />
The message sent from MAES or SAES was larger than the user area<br />
provided. This error typically occurs when a user-written program attempts<br />
to drive the link <strong>and</strong> the AESIOLEN field is not set properly.<br />
Transaction Driver <strong>Messages</strong> 2-17
Change language