"Each file could be created
> unique by composing its name based on a sequential numbering scheme from
> the
> results of a LISTF."
Or maybe have the job check who streamed it and use the job/session number
as (part of) the file name.
Something like (only the 1st two lines are tested)
setvar BY_SESS_NUM WORD(HPSTREAMEDBY,"()",2) - "#" - "S" - "J"
setvar FILE_BASE "F" + rht("00000!BY_SESS_NUM", 6)
if finfo ("!FILE_BASE.group.acct", "exists")
purge or rename it something like j123a, j123b, etc
endif
build !FILE_BASE.group.acct;otherparms......
(I'm zero-padding or truncating the session number to ensure a legal file
name and make them :listf in the order I would want).
Dave (once again, we're talking about locking in the prison system, right?)
Powell
----- Original Message -----
From: "Eric Sand" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Monday, April 13, 2009 14:56
Subject: Re: [HP3000-L] How to see what's locked in a TurboIMAGE database
> Hi Walter,
> To keep things simple, I would just create a "RELEASED" job that can
> execute DBUTIL with the proper passwords to the DB that you want to
> examine
> and direct the output to a file that anyone can read. The job that wants
> the
> locking info would stream this DBUTIL job using the "COMMAND" intrinsic
> and
> then parse the output file. This could be done by the "CALLING" program
> repeatedly if needed and report its findings. Each file could be created
> unique by composing its name based on a sequential numbering scheme from
> the
> results of a LISTF.
>
> Hope my suggestion is useful...
>
> Eric Sand
>
>
>
> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf
> Of Walter J. Murray
> Sent: Sunday, April 12, 2009 12:26 PM
> To: [log in to unmask]
> Subject: [HP3000-L] How to see what's locked in a TurboIMAGE database
>
> Greetings,
>
> I am looking for a way to permit ordinary users (programmers and support
> staff) to see who is using a TurboIMAGE database, and what locks are in
> effect and are pending--the information you would see with DBUTIL using
> SHOW ... USERS and SHOW ... LOCKS or SHOW ... ALL.
>
> I have to work within these constraints: (1) Can't let them log on with
> SM capability. (2) Can't let them log on as the database creator. (3)
> Can't reveal the password on the MPEX GOD program. (4) Can't reveal the
> password on DBUTIL.
>
> Any suggestions? Any utility to do this?
>
> My best idea so far is to set up a command file that would use the MPEX
> %WITHCAPS command to grant SM capability temporarily, then run DBUTIL.
>
> Walter
>
> Walter J. Murray
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
