> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On
> Behalf Of Johnson, Tracy
> Sent: Tuesday, May 06, 2008 1:42 PM
> To: [log in to unmask]
> Subject: Re: Minisoft/ODBC Help Please
> 
> Minisoft has a program called "Server Console"
> 
> On thier "ODBC" web page look down at the lower left for "Downloadable
> Utilities".  (DO NOT confuse it with the "ODBC Updates" link.)
> 
> It will not tell you what files are being moved or where, but it will
> tell you "who" is accessing ODBC.  Then I suppose you can confront any
> such user and demand they tell you what they are doing (presuming they
> even know.)
> 
> If you want to be more surreptitious about what is being accessed (but
> not where,) MPEX's LISTF, ACCESS should tell you which files are being
> accessed by the ODBC job.
> 
> Side by side with the Server Console above, you should be able to say
> "Aha!  So and so is accessing such and such file, and name the PIN
> number."
> 
> (The server console will also let you kill the user PIN without
> aborting
> the entire ODBC job.)
> 
> Tracy Johnson
> Measurement Specialties Inc.
> BT
> 

There is also a utility on the HP that you can use to list open
connections. I have a command file I wrote to manage the odbc server:

PARM CMD
IF UPS("!CMD") = "START" THEN
  RUN MPEX.PUB.VESOFT; &
  INFO="SETVAR MSJOBCOUNT, JSCOUNT('MSJOB,MGR.MINISOFT')"
  IF !MSJOBCOUNT > 0 THEN
    RUN MSJOBCMD.MM.MINISOFT; &
    PARM=4;INFO="4|30006|0|ODBCSRVR.MM.MINISOFT;PRI=CS S W"
    RUN MSJOBCMD.MM.MINISOFT; &
    PARM=4;INFO="4|31006|0|ODBCTEST.MM.MINISOFT;PRI=CS S W"
  ELSE
    STREAM MSJOB.MM.MINISOFT;JOBQ=SYSJOBS
  ENDIF
ELSEIF UPS("!CMD") = "STOP" THEN
  RUN MSJOBCMD.MM.MINISOFT;PARM=2;INFO="30006"
  RUN MSJOBCMD.MM.MINISOFT;PARM=2;INFO="31006"
ELSEIF UPS("!CMD") = "LIST" THEN
  RUN MSJOBCMD.MM.MINISOFT;PARM=0;INFO="30006"
  RUN MSJOBCMD.MM.MINISOFT;PARM=0;INFO="31006"
ELSE
  ECHO
  ECHO INVALID OPTION (!CMD)
  ECHO
  ECHO VALID OPTIONS ARE START/STOP/LIST
  ECHO
ENDIF

The sample above shows my 2 servers, production and test, that it
performs all options on.

ODBC START
ODBC LIST
ODBC STOP

The above commands cover the majority of my needs during batch
processing and troubleshooting. But you will notice that STOP does not
abort the MSJOB listener, it just shuts down the ODBC server which
avoids shutting down any other Minisoft products or the windows based
console Tracy mentions above. This comes in handy for me as I use the
command file inside batch jobs, that needs exclusive access to some
files, and use the windows console for troubleshooting.

Either way I find MSJOBCMD.MM.MINISOFT quite handy.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *