# Zowe runtime problems

**URL:** <https://community.openmainframeproject.org/t/zowe-runtime-problems/351>\
**Category:** Zowe\
**Created:** [May 1, 2019, 3:48pm UTC](https://community.openmainframeproject.org/t/zowe-runtime-problems/351 "2019-05-01T15:48:37Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![John.Davies](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.openmainframeproject.org/john.davies/32/801_2.png) [@John.Davies](https://community.openmainframeproject.org/u/John.Davies)\
**Post date:** [May 1, 2019, 3:48pm UTC](https://community.openmainframeproject.org/t/zowe-runtime-problems/351/1 "2019-05-01T15:48:37Z")

</div>

To determine the cause of Zowe runtime problems, a basic first step is to run the verify script on USS.

```auto
cd ZOWE_ROOT_DIR/scripts
zowe-verify.sh

```

The `ZOWE_ROOT_DIR` is the directory where you installed the Zowe runtime files.

You can also run a script to check the pre-requisites, even after Zowe is installed. You will see errors about port conflicts and possibly available disk space if Zowe is already installed and running - this is normal.

```auto
cd INSTALL_DIR/install
zowe-check-prereqs.sh

```

The `INSTALL_DIR` is the directory where you un-PAXed the Zowe PAX file.

Neither of these scripts changes your system, so you can run them at any time.