Slide 1

Slide notes: When it is necessary for Support Staff to perform some administrative functions at the QM Database Command Level, then a QM Console Session is the best tool. It is only available on the Server itself, so if one does not have access to the Server directly, then a Telnet Session is the next choice. In this tutorial, we see how to Log On a QM Console Session, and how we can get to any Datamart with such a Session.

 

 

 

 

Slide 2

Slide notes: We choose START, then ALL PROGRAMS, and look for QM on the list.

 

 

 

Slide 3

Slide notes:

 

 

 

Slide 4

Slide notes: From the options in the QM selection, we choose QM Console.

 

 

 

Slide 5

Slide notes: And this will open a QM logon prompt, provided that the QM Database is currently running.

 

 

 

Slide 6

Slide notes: If we see "QMSYS" listed in brackets, as shown here, then we can just press ENTER to go directly to the QMSYS account, but if another name is listed in brackets, then it is necessary to type QMSYS specifically. In this case, we will type QMSYS anyway.

 

 

 

Slide 7

Slide notes: The Console User is allowed into QMSYS, which is the controlling Account or Datamart for the QM Database. Here we can directly perform the administrative actions that we may wish to perform, or we can log to any IES Datamart from here.

 

 

 

 

Slide 8

Slide notes: If we log to another IES Datamart, for example INFOLAB, then our entry will be subject to IES security, and we will have to log on with an IES Usercode and Password, and this UserCode must have access to the TCL process in IES, for the Datamart we log to.

 

 

 

Slide 9

Slide notes:

 

 

 

Slide 10

Slide notes:

 

 

 

Slide 11

Slide notes: We can also log to any other IES Datamart that we may need to go to in order to perform administrative actions, as long as this UserCode has access to TCL in that Datamart.

 

 

 

Slide 12

Slide notes: When we have concluded the actions we wish to perform, then we sign off by typing "off" to end the session.

 

 

 

Slide 13

Slide notes: