29.06.2013 Views

AionDS Messages and Codes Guide

AionDS Messages and Codes Guide

AionDS Messages and Codes Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>AionDS</strong> runtime errors<br />

.........................................................................................................................................................................................................˝..........................................<br />

37378<br />

1-184 <strong>AionDS</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong><br />

AION views are not supported for importing<br />

<strong>AionDS</strong> does not allow you to import views because it cannot guarantee the<br />

view will be valid against the database.<br />

.........................................................................................................................................................................................................˝..........................................<br />

37379<br />

SQL “close cursor” failed<br />

This error might occur if the close cursor function attempted to close an<br />

invalid cursor or a cursor that wasn’t open.<br />

To find out more information about why the “close cursor” function failed,<br />

use the DBINFO KDL statement to retrieve the SQL database error code<br />

<strong>and</strong> error message.<br />

For more information: See the <strong>AionDS</strong> I/O Reference for more<br />

information about DBINFO.<br />

.........................................................................................................................................................................................................˝..........................................<br />

37380<br />

Unable to load local static SQL access module (MVS)<br />

This error occurs when an HPO knowledge base attempted to execute a local,<br />

static SQL request but the static SQL access module was not in ADSLIB or<br />

STEPLIB of the region.<br />

.........................................................................................................................................................................................................˝..........................................<br />

37381<br />

Unable to load remote static SQL access module (MVS)<br />

This error occurs when an HPO knowledge base attempted to execute a<br />

remote, static SQL request but the static SQL access module was not in<br />

DFHRPL or STEPLIB of the IMS region.<br />

.........................................................................................................................................................................................................˝..........................................<br />

42510<br />

The WHAT comm<strong>and</strong> is not valid here<br />

The WHAT comm<strong>and</strong> is not available within the What monitor or the<br />

Other Sources monitor. Within the Explanation facility, the WHAT<br />

comm<strong>and</strong> is only valid from the How <strong>and</strong> Why monitors.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!