AionDS Messages and Codes Guide
AionDS Messages and Codes Guide AionDS Messages and Codes Guide
MAESLOG messages .........................................................................................................................................................................................................˝.......................................... 2009 6-8 AionDS Messages and Codes MAESLGON MAES received a LOGON request. This log message is issued at entry to MAESLGON, but before MAES determines if the request is from a valid session partner. .........................................................................................................................................................................................................˝.......................................... 2010 MAESLGON In response to a LOGON request, MAES issues a VTAM OPNDST call to the requester. This MAESLOG message shows the VTAM RPL and node initialization block (NIB) used for the successful OPNDST. .........................................................................................................................................................................................................˝.......................................... 2011 MAESLUNM The value specified for WIN was not a valid number. .........................................................................................................................................................................................................˝.......................................... 2012 MAESLUNM The value specified for MAX was not a valid number. .........................................................................................................................................................................................................˝.......................................... 2013 MAESNSEX In certain VTAM error situations (typically when a session is being unbound) the network services exit is given control. This log message reflects that fact and also logs the header information which is used to determine the reason for the error condition. .........................................................................................................................................................................................................˝.......................................... 2014 MAESRCVE After an outstanding VTAM RECEIVE call is completed, another RECEIVE call is issued. This log message indicates that the RECEIVE call can be completed with a message from any session bound to MAES which is not already in a specific mode with another MAES component.
MAESLOG messages .........................................................................................................................................................................................................˝.......................................... 2015 MAESLUNM The value specified for RU was not a valid number. .........................................................................................................................................................................................................˝.......................................... 2016 MAESLUNM The value of RU is either less than 256 or not a power of 2 (256, 512, 1024, and so on). .........................................................................................................................................................................................................˝.......................................... 2017 MAESSBND MAESSBND constructs the request unit for binding to another session. This log message shows the contents of the BIND image. .........................................................................................................................................................................................................˝.......................................... 2018 MAESSCIP A VTAM SCIP exit is given control. This log message indicates that one of the following conditions occurred: ■ Request Recovery (RQR VTAM message) ■ Set and TEST Sequence Numbers (STSN VTAM message) ■ bind request ■ session unbind ■ clear MAESSCIP determines which condition occurred and acts accordingly. .........................................................................................................................................................................................................˝.......................................... 2019 MAESSCIP The MAES SCIP exit receives an UNBIND request. The reason code for the UNBIND request is logged with this log message. Typically, an UNBIND request occurs when the partner session terminates. MAESLOG Messages 6-9
- 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
- Page 283 and 284: MAESLOG messages ..................
- Page 285: MAESLOG messages ..................
- Page 289 and 290: MAESLOG messages ..................
- Page 291 and 292: MAESLOG messages ..................
- Page 293 and 294: MAESLOG messages ..................
- Page 295 and 296: MAESLOG messages ..................
- Page 297 and 298: MAESLOG messages ..................
- Page 299 and 300: MAESLOG messages Since this error r
- Page 301 and 302: MAESLOG messages ..................
- Page 303 and 304: MAESLOG messages ..................
- Page 305 and 306: MAESLOG messages ..................
- Page 307 and 308: MAESLOG messages ..................
- Page 309 and 310: MAESLOG messages ..................
- Page 311 and 312: MAESLOG messages ..................
- Page 313 and 314: MAESLOG messages ..................
- Page 315 and 316: MAESLOG messages ..................
- Page 317 and 318: MAESLOG messages ..................
- Page 319 and 320: MAESLOG messages ..................
- Page 321 and 322: MAESLOG messages ■ The node is ac
- Page 323 and 324: MAESLOG messages ..................
- Page 325 and 326: MAESLOG messages ..................
- Page 327 and 328: MAESLOG messages ..................
- Page 329 and 330: MAESLOG messages ..................
- Page 331 and 332: MAESLOG messages ..................
- Page 333 and 334: MAESLOG messages ..................
- Page 335 and 336: MAESLOG messages ..................
MAESLOG messages<br />
.........................................................................................................................................................................................................˝..........................................<br />
2015<br />
MAESLUNM<br />
The value specified for RU was not a valid number.<br />
.........................................................................................................................................................................................................˝..........................................<br />
2016<br />
MAESLUNM<br />
The value of RU is either less than 256 or not a power of 2 (256, 512, 1024,<br />
<strong>and</strong> so on).<br />
.........................................................................................................................................................................................................˝..........................................<br />
2017<br />
MAESSBND<br />
MAESSBND constructs the request unit for binding to another session. This<br />
log message shows the contents of the BIND image.<br />
.........................................................................................................................................................................................................˝..........................................<br />
2018<br />
MAESSCIP<br />
A VTAM SCIP exit is given control. This log message indicates that one of<br />
the following conditions occurred:<br />
■ Request Recovery (RQR VTAM message)<br />
■ Set <strong>and</strong> TEST Sequence Numbers (STSN VTAM message)<br />
■ bind request<br />
■ session unbind<br />
■ clear<br />
MAESSCIP determines which condition occurred <strong>and</strong> acts accordingly.<br />
.........................................................................................................................................................................................................˝..........................................<br />
2019<br />
MAESSCIP<br />
The MAES SCIP exit receives an UNBIND request. The reason code for the<br />
UNBIND request is logged with this log message. Typically, an UNBIND<br />
request occurs when the partner session terminates.<br />
MAESLOG <strong>Messages</strong> 6-9