HP3000-L Archives

March 1998, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Lee Gunter <[log in to unmask]>
Reply To:
Lee Gunter <[log in to unmask]>
Date:
Mon, 2 Mar 1998 09:06:17 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (63 lines)
I'm not sure what might be causing your problem, but have you thought of
eliminating the DBUTIL step altogether?  If you're already using MPEX, you
can do something like:

     % listf @[log in to unmask]@(intcode=-400),6  > temp         (list root files, fully
qualified, to a temp file)
     % listf ^temp, db   > outfile            (pass temp file to "listf,
db")
     <scan 'outfile' for capacities>

to get a capacity listing.  You could also do this in one step by "or"-ing
all the possible INTCODEs (-401=std dataset; -408=jumbo chunk control file;
-409=jumbo chunk file, etc.), but this could conceivably miss a new dataset
type.

Lee Gunter
Regence Blue Cross Blue Shield of Oregon / Regence HMO Oregon

mailto:[log in to unmask]
voice...503-375-4498     fax.....503-375-4401
==========================================================
The opinions expressed, here, are mine and mine alone, and do not
necessarily reflect those of my employer.




From: [log in to unmask] on 03/02/98 06:41 AM

Please respond to [log in to unmask]


To:   [log in to unmask]
cc:    (bcc: Lee Gunter/BCBSO/TBG)
Subject:  Strange output from DBUTIL




Hi there DB Gurus!
I am experiencing some strange output from DBUTIL when trying to capture
dataset capacities.
Here is what I'm doing:
1.  Using MPEX to get a listing of all Image root files on a system
2.  Using this list as input to DBUTIL to create a list of all datasets
capacities on a system
3.  Piping this list to a scanning utility to perform predictive expansion
on datasets.
This at least is the goal! It is not feasible to create "creator" access to
the database with QUERY, so I am using the MANAGER.SYS and DBUTIL SHOW
<database> CAPACITY approach, because this must work with several thousand
database on many widely distributed network nodes.
My problem is that when I use the SHOW <database> CAPACITY command from
MANAGER.SYS, I <sometimes> get a message that the specified account name is
too long ( it isn't, it's only 7 characters!). I can get in using QUERY and
do a FO SETS, because in some instances I know the available passwords.
HOwever, Each site is able to change things to suit themselves, and I can't
always do this.
Anybody else ever encountered this strange behavior? Am I overlooking
something "Duh"ish? Is this merely a Monday Morning Manifestation?
Your help is eagerly solicited!
Tony "Scratching his head in frustration" Furnivall

ATOM RSS1 RSS2