AionDS Messages and Codes Guide
AionDS Messages and Codes Guide AionDS Messages and Codes Guide
MAESLOG messages .........................................................................................................................................................................................................˝.......................................... 4005 6-18 AionDS Messages and Codes MAESALRU This log message records request unit memory allocation and request unit size. As part of the initialization process, MAES allocates memory for request units. .........................................................................................................................................................................................................˝.......................................... 4006 MAESAUTO As part of startup or by virtue of a MONITOR request to acquire a partner, MAES automatically acquires sessions with a session partner. This log message is issued immediately after the VTAM REQSESS request. .........................................................................................................................................................................................................˝.......................................... 4007 MAESBECB This log message is issued after storage was allocated for the list of event control blocks (ECBs). MAES maintains a list of ECBs. .........................................................................................................................................................................................................˝.......................................... 4008 MAESBRPL During initialization, MAES constructs VTAM control blocks for all potential consultations. This log message indicates that the VTAM RPL request was built. .........................................................................................................................................................................................................˝.......................................... 4009 MAESDBUG During initialization, MAES attempts to load the MAESDBUG program which represents an optimized version of a PLATINUM-supplied knowledge base (debug knowledge base) to analyze problems. This log message indicates that the module was found and that the debug knowledge base was activated.
MAESLOG messages .........................................................................................................................................................................................................˝.......................................... 4011 MAESLOGM MAES can dynamically link to certain external programs (such as the debug knowledge base). The external programs can add log messages to the MAESLOG dataset under this ID. These log messages can be informational or reflect error conditions. For example, execution parameter processing errors are recorded in MAESLOG. MAESPARM and PMEMBER processing messages are also associated with log message 4011. .........................................................................................................................................................................................................˝.......................................... 4012 MAESLUNM This log message indicates that the MAESLUNM analysis function was entered. .........................................................................................................................................................................................................˝.......................................... 4013 MAESLUNM This log message is issued when a parsing error is found in the MAESLUNM entry. This log message describes the problem. Correct the error and resubmit the MAES JCL. .........................................................................................................................................................................................................˝.......................................... 4014 MAESLUNM This log message shows the record read from the MAESLUNM file before any processing is done. .........................................................................................................................................................................................................˝.......................................... 4015 MAESPARM This log message has no text. This log message precedes the remaining log messages that are issued when the execute parameters are parsed and analyzed. .........................................................................................................................................................................................................˝.......................................... 4016 MAESPRLD This log message indicates that the preload function was invoked. MAESLOG Messages 6-19
- 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 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: 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 ..................
- 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 ...............
MAESLOG messages<br />
.........................................................................................................................................................................................................˝..........................................<br />
4011<br />
MAESLOGM<br />
MAES can dynamically link to certain external programs (such as the debug<br />
knowledge base). The external programs can add log messages to the<br />
MAESLOG dataset under this ID. These log messages can be informational<br />
or reflect error conditions. For example, execution parameter processing<br />
errors are recorded in MAESLOG. MAESPARM <strong>and</strong> PMEMBER<br />
processing messages are also associated with log message 4011.<br />
.........................................................................................................................................................................................................˝..........................................<br />
4012<br />
MAESLUNM<br />
This log message indicates that the MAESLUNM analysis function was<br />
entered.<br />
.........................................................................................................................................................................................................˝..........................................<br />
4013<br />
MAESLUNM<br />
This log message is issued when a parsing error is found in the MAESLUNM<br />
entry. This log message describes the problem. Correct the error <strong>and</strong><br />
resubmit the MAES JCL.<br />
.........................................................................................................................................................................................................˝..........................................<br />
4014<br />
MAESLUNM<br />
This log message shows the record read from the MAESLUNM file before<br />
any processing is done.<br />
.........................................................................................................................................................................................................˝..........................................<br />
4015<br />
MAESPARM<br />
This log message has no text. This log message precedes the remaining log<br />
messages that are issued when the execute parameters are parsed <strong>and</strong><br />
analyzed.<br />
.........................................................................................................................................................................................................˝..........................................<br />
4016<br />
MAESPRLD<br />
This log message indicates that the preload function was invoked.<br />
MAESLOG <strong>Messages</strong> 6-19