AionDS Messages and Codes Guide
AionDS Messages and Codes Guide AionDS Messages and Codes Guide
AionDS runtime errors .........................................................................................................................................................................................................˝.......................................... 20510 1-134 AionDS Messages and Codes RKB error - Unexpected error terminating remote consultation An error was encountered by CPO in terminating the conversation with the remote data server or remote MAES. Check the MAESLOG for any problems with the termination of the consultation. Check the MVS Console Log for any VTAM error messages. If the remote data server is CICS, check the CICS log for related error messages. .........................................................................................................................................................................................................˝.......................................... 20511 RKB error - Bad HPO name The remote MAES system was unable to find the HPO knowledge base specified. Check that the name specified for the REMOTE KB process object is a load module in a library included in the STEPLIB DD of the remote MAES system. .........................................................................................................................................................................................................˝.......................................... 20512 Remote process object not supported The AionDS remote process routines REMOTE CONNECT and REMOTE KB require the Cooperative Processing Option (CPO) which is not installed. .........................................................................................................................................................................................................˝.......................................... 20515 LU6.2 session error - Null message returned An empty message was received from the remote system. .........................................................................................................................................................................................................˝.......................................... 20516 RKB error - Remote KB attempted to display a user message The remote knowledge base attempted to display a message. This is not allowed with CPO processing. Remove the display or the condition which caused the display in the remote knowledge base. To discover what caused this condition, check the AionDS system log and consultation trace of the remote MAES system.
AionDS runtime errors .........................................................................................................................................................................................................˝.......................................... 20546 LU6.2 session error - session ALLOCATION failed CPO was unable to allocate a session with the host. Check that the configuration file has been set up with the suggested parameters. Also, check the SNA profile and the PARTNER LU profile for the partner you are attempting to access and the transmission profile. This error can also occur if you attempt to use DL/I or DB2 and it has not been activated in the remote system. .........................................................................................................................................................................................................˝.......................................... 20547 LU6.2 session error - SEND failed CPO was unable to send a message or request through VTAM to the remote system. Check that the remote system is still active and functioning. Check the MVS console or Netview for VTAM error conditions. .........................................................................................................................................................................................................˝.......................................... 20548 LU6.2 session error - RECEIVE failed Communication with the host abnormally terminated while CPO was waiting for a response. Check that the host system is active, that the remote system is active and is not in a loop. .........................................................................................................................................................................................................˝.......................................... 20549 Communications Client rejected APPC startup See your vendor’s communication client documentation. .........................................................................................................................................................................................................˝.......................................... 20561 LU6.2 session error - Invalid system name The system name specified in the input record passed by a REMOTE CONNECT or REMOTE KB process object referred to an invalid name. Check the Communications Client Configuration file for valid names. AionDS Runtime Errors 1-135
- Page 97 and 98: AionDS runtime errors .............
- Page 99 and 100: AionDS runtime errors At edit time
- Page 101 and 102: AionDS runtime errors .............
- Page 103 and 104: AionDS runtime errors .............
- Page 105 and 106: AionDS runtime errors .............
- Page 107 and 108: AionDS runtime errors .............
- Page 109 and 110: AionDS runtime errors .............
- Page 111 and 112: AionDS runtime errors .............
- Page 113 and 114: AionDS runtime errors Reminder: In
- Page 115 and 116: AionDS runtime errors .............
- Page 117 and 118: AionDS runtime errors .............
- Page 119 and 120: AionDS runtime errors .............
- Page 121 and 122: AionDS runtime errors .............
- Page 123 and 124: AionDS runtime errors .............
- Page 125 and 126: AionDS runtime errors .............
- Page 127 and 128: AionDS runtime errors .............
- Page 129 and 130: AionDS runtime errors .............
- Page 131 and 132: AionDS runtime errors .............
- Page 133 and 134: AionDS runtime errors .............
- Page 135 and 136: AionDS runtime errors .............
- Page 137 and 138: AionDS runtime errors .............
- Page 139 and 140: AionDS runtime errors .............
- Page 141 and 142: AionDS runtime errors .............
- Page 143 and 144: AionDS runtime errors .............
- Page 145 and 146: AionDS runtime errors AionDS suppor
- Page 147: AionDS runtime errors .............
- Page 151 and 152: AionDS runtime errors .............
- Page 153 and 154: AionDS runtime errors .............
- Page 155 and 156: AionDS runtime errors .............
- Page 157 and 158: AionDS runtime errors .............
- Page 159 and 160: AionDS runtime errors .............
- Page 161 and 162: AionDS runtime errors .............
- Page 163 and 164: AionDS runtime errors .............
- Page 165 and 166: AionDS runtime errors .............
- Page 167 and 168: AionDS runtime errors .............
- Page 169 and 170: AionDS runtime errors .............
- Page 171 and 172: AionDS runtime errors .............
- Page 173 and 174: AionDS runtime errors .............
- Page 175 and 176: AionDS runtime errors .............
- Page 177 and 178: AionDS runtime errors .............
- Page 179 and 180: AionDS runtime errors .............
- 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 .............
<strong>AionDS</strong> runtime errors<br />
.........................................................................................................................................................................................................˝..........................................<br />
20546<br />
LU6.2 session error - session ALLOCATION failed<br />
CPO was unable to allocate a session with the host. Check that the<br />
configuration file has been set up with the suggested parameters. Also, check<br />
the SNA profile <strong>and</strong> the PARTNER LU profile for the partner you are<br />
attempting to access <strong>and</strong> the transmission profile. This error can also occur if<br />
you attempt to use DL/I or DB2 <strong>and</strong> it has not been activated in the remote<br />
system.<br />
.........................................................................................................................................................................................................˝..........................................<br />
20547<br />
LU6.2 session error - SEND failed<br />
CPO was unable to send a message or request through VTAM to the remote<br />
system. Check that the remote system is still active <strong>and</strong> functioning. Check<br />
the MVS console or Netview for VTAM error conditions.<br />
.........................................................................................................................................................................................................˝..........................................<br />
20548<br />
LU6.2 session error - RECEIVE failed<br />
Communication with the host abnormally terminated while CPO was<br />
waiting for a response. Check that the host system is active, that the remote<br />
system is active <strong>and</strong> is not in a loop.<br />
.........................................................................................................................................................................................................˝..........................................<br />
20549<br />
Communications Client rejected APPC startup<br />
See your vendor’s communication client documentation.<br />
.........................................................................................................................................................................................................˝..........................................<br />
20561<br />
LU6.2 session error - Invalid system name<br />
The system name specified in the input record passed by a REMOTE<br />
CONNECT or REMOTE KB process object referred to an invalid name.<br />
Check the Communications Client Configuration file for valid names.<br />
<strong>AionDS</strong> Runtime Errors 1-135
Change language