AionDS Messages and Codes Guide
AionDS Messages and Codes Guide AionDS Messages and Codes Guide
MAESLOG messages .........................................................................................................................................................................................................˝.......................................... 12022 6-44 AionDS Messages and Codes MAESSYNA All VTAM request errors, other than OPEN and CLOSE requests, force the SYNAD exit to be executed. MAES logs the return code and feedback information in the VTAM RPL with this message. If the debug knowledge base is active, more detailed information is written to MAESLOG which can help in analyzing the problem. .........................................................................................................................................................................................................˝.......................................... 12023 MAESSYNA Certain VTAM errors can be retried. If the MAES VTAM SYNAD exit determines that a retry is appropriate, a VTAM EXECRPL is executed. This message indicates that the request was rejected. The RPL is logged so that PLATINUM Technical Support for AionDS can debug the problem. .........................................................................................................................................................................................................˝.......................................... 12024 MAESRECP MAES received a reached recovery node (RRN) VTAM protocol message from the session partner. MAES calls MAESRRN to respond appropriately. .........................................................................................................................................................................................................˝.......................................... 12025 MAESXLN By returning its own XLN message, MAES responds to an exchange log names (XLN) request from a session partner. If the VTAM request fails, MAESSYNA issues an error message. The code that issued the SEND request issues this log message. .........................................................................................................................................................................................................˝.......................................... 12026 MAESSECS MAES received a BIND request, but the name of the logical unit attempting the BIND was not found in the MAESLUNM dataset. Determine if the attempt to bind was valid. If the BIND request was valid, correct the MAESLUNM dataset before resubmitting the request to MAES. You can also add a new potential partner session using the MONITOR knowledge base if you are unable to terminate MAES to make the correction.
MAESLOG messages .........................................................................................................................................................................................................˝.......................................... 12118 MAESSECS The session control blocks are dumped after a BIND fails. A log message header (with the same log message number) separates each session control block dump. .........................................................................................................................................................................................................˝.......................................... 12140 MAESERR A format header type 7 (FMH7) was sent to the transaction driver. .........................................................................................................................................................................................................˝.......................................... 12145 MAESERR A status message was sent to the transaction driver. This log message contains the status message in hexadecimal form. .........................................................................................................................................................................................................˝.......................................... 12240 MAESRCV1 A VTAM RECEIVE call was made to a service manager session. .........................................................................................................................................................................................................˝.......................................... 12250 MAESRESP A VTAM response was sent to the transaction driver. .........................................................................................................................................................................................................˝.......................................... 12500 SAESGET This log message is issued when a VTAM protocol message SEND fails. For instance, SAESGET detects a VTAM SHUTD request and attempts to respond. If the response fails, log message 12500 is issued. MAESLOG Messages 6-45
- 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 and 286: MAESLOG messages ..................
- Page 287 and 288: 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: MAESLOG messages ■ The node is ac
- 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 ..................
- Page 337 and 338: Chapter 7 AionDS Fatal System Error
- Page 339 and 340: Overview Only at edit time can the
- Page 341 and 342: Fatal system errors ...............
- Page 343 and 344: Fatal system errors ...............
- Page 345 and 346: Fatal system errors ...............
- Page 347 and 348: Chapter 8 AionDS System Log .......
- Page 349 and 350: Examining the system log database T
- Page 351 and 352: Execution messages Examining the sy
- Page 353 and 354: Consultation messages Examining the
- Page 355 and 356: Examining the system log ..........
- Page 357 and 358: Examining the system log ..........
- Page 359 and 360: DL/I Messages Examining the system
- Page 361: AionDS Messages and Codes DC0431
MAESLOG messages<br />
.........................................................................................................................................................................................................˝..........................................<br />
12022<br />
6-44 <strong>AionDS</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong><br />
MAESSYNA<br />
All VTAM request errors, other than OPEN <strong>and</strong> CLOSE requests, force the<br />
SYNAD exit to be executed. MAES logs the return code <strong>and</strong> feedback<br />
information in the VTAM RPL with this message. If the debug knowledge<br />
base is active, more detailed information is written to MAESLOG which can<br />
help in analyzing the problem.<br />
.........................................................................................................................................................................................................˝..........................................<br />
12023<br />
MAESSYNA<br />
Certain VTAM errors can be retried. If the MAES VTAM SYNAD exit<br />
determines that a retry is appropriate, a VTAM EXECRPL is executed. This<br />
message indicates that the request was rejected. The RPL is logged so that<br />
PLATINUM Technical Support for <strong>AionDS</strong> can debug the problem.<br />
.........................................................................................................................................................................................................˝..........................................<br />
12024<br />
MAESRECP<br />
MAES received a reached recovery node (RRN) VTAM protocol message<br />
from the session partner. MAES calls MAESRRN to respond appropriately.<br />
.........................................................................................................................................................................................................˝..........................................<br />
12025<br />
MAESXLN<br />
By returning its own XLN message, MAES responds to an exchange log<br />
names (XLN) request from a session partner. If the VTAM request fails,<br />
MAESSYNA issues an error message. The code that issued the SEND<br />
request issues this log message.<br />
.........................................................................................................................................................................................................˝..........................................<br />
12026<br />
MAESSECS<br />
MAES received a BIND request, but the name of the logical unit attempting<br />
the BIND was not found in the MAESLUNM dataset. Determine if the<br />
attempt to bind was valid. If the BIND request was valid, correct the<br />
MAESLUNM dataset before resubmitting the request to MAES. You can<br />
also add a new potential partner session using the MONITOR knowledge<br />
base if you are unable to terminate MAES to make the correction.