Using the 7.3 script version fixes this problem
but now another anomaly appears. It provides the
error:
Group different than current logon::: DBFILE##.DBGROUP.ACCOUNT
(DBGROUP:::LOGONGROUP)
if you are in a different group than where the file resides.
It appears the 7.217 script didn't care if you used @.@ for the fileset,
it made the attempt whether you were in the logon group or not.
Tracy Johnson
MSI Schaevitz Sensors
-----Original Message-----
From: Tim Joseph [mailto:[log in to unmask]]
Sent: Thursday, December 14, 2000 10:53 AM
To: [log in to unmask]
Subject: Re: DBGENALT Won't !EOF
Hello,
Bradmark wrote the DBGENALT command file many years ago and contributed it
to the VEsoft tape. This is a terrific usage of MPEX's fileset
ability. Recently this command file has been updated to handle JUMBO,
masters with B-Trees and dynamic datasets and to be compatible with
DBGENERAL version 7.3.
When DBGENERAL version 7.3 is run with the old command file, it may hang as
you describe due to an additional prompt in the batch dialog of master
capacity change (now batch and on-line prompting sequences are the
same). This change has been highlighted in the release notes.
To cause the older version of the command file to continue to function
correctly with DBGENERAL version 7.3, please add a line to the command file
prior to the DBGENERAL execution:
:SETJCW DBGUSERVERSION = 7217
which will cause DBG to prompt (in batch or when i/o is redirected to a
file -- as in dbgenalt) as it did prior to 7.3, thus making the dialog
consistent with the old dbgenalt command file.
The only thing you 'loose' with the new command file is the ability to
spawn jobs for each unique creator/group/account. I believe the new
command file can be adapted to implement this, but for now the command file
must be launched as the creator in the group and account where the
database(s) exists.
Thanks,
tj
>DBGENALT Command for DBGeneral version 7.3
>
>
>DBGENALT is a command file that requires MPEX from Vesoft Inc. This
>command file can be used to manage capacities of databases by using MPEX
>to control the fileset being managed and DBGeneral to perform the capacity
>change.
>
>SYNTAX
>
>%DBGENALT fileset, percent, password
>
>fileset may be any legal MPEX fileset; however, only datasets in the logon
>group created by the logon user will be managed.
>percent ratio of entry count over new capacity. Specifying .7, indicates
>the set's capacity should be adjusted such that the set is 70% full.
>Password DBGeneral password
>
>Sample command
>
>:mpex
>%DBGENALT @.macsdata.sgaii(dbsetfullness>.7), .7, testa
>Changes all datasets in macsdata that are more than 70% (.7) full, to
>become 70% full.
>
>
>DBGENALT has been enhanced to support:
>
>DBGENALT now supports JUMBO Masters, JUMBO Details, Dynamic Master
>Datasets, Dynamic Detail Datasets and Masters with B-trees. Previous
>versions encountered problems with the MPEX looping constructs such that
>the same dataset was changed multiple times and others not at all.
>
>By default, DBGENALT will not manage JUMBO or Dynamic datasets; however,
>you can tell DBGENALT that you want to manage JUMBOs or Dynamic dataset by
>setting the variables shown below. Note that by default dynamic sets have
>their maximum capacity set equal to 5 times the new capacity and the
>increment to one tenth the new capacity. These defaults can be changed
>directly in the command file.
>:SETVAR DBGENALT_JUMBO TRUE
>:SETVAR DBGENALT_DYNAMIC TRUE
>
>
>DBGENERAL 7.3 dialog changes
>
>Master capacity changes in batch (or redirected as in a command file) with
>DBGeneral version 7.3 have an extra prompt. The old DBGENALT command file
>will hang when a master dataset is managed using DBGeneral version
>7.3. You should convert to this new command file (DBGENALT.mpex.bradmark)
>to insure smooth operation. Alternatively or as a temporary workaround,
>you may add a line to the old command file:
>setjcw dbguserversion=7217,
>to utilize the older dialog. The new command file is only compatible with
>DBGeneral version 7.3.
>
>
>DBGENALT Installation
>
>DBGENALT is found in the MPEX group of the BRADMARK account
>(dbgenalt.mpex.bradmark) and executed by specifying the fully qualified
>file name. You must copy this file into the cmd22 group of the VEsoft
>account (dbgenalt.cmd22.vesoft) and execute by typing 'DBGENALT'. If you
>try to use the file as DBGENALT.MPEX.BRADMARK, MPEX will see that there is
>a file DBGENALT in cmd22.vesoft and use it instead !
>
>
>DBGENALT will manage databases in one group and one creator
>
>DBGENALT focuses on managing one or more databases created by the logon
>user in one group. Previously, DBGENALT would permit multiple accounts,
>groups and creators by using a recursive algorithm to stream itself for
>each unique creator/group/account of the fileset specified. This
>generally worked well; however, there were some issues. At times this
>spawning effect would produce a confusing web of jobs. Also, multiple
>jobs may be streamed in the same group by the old DBGENALT's recursive
>behavior, which is not permitted by DBGeneral and must be avoided with job
>queues or limits. Overall, most users seem to be using DBGENALT to manage
>a single database or several databases in one group that all have the same
>creator.
>
>
>DBGENALT Dialog messages
>
>%DBGENALT @,.7,testa
>Version 2.05 For Standard, JUMBO, B-tree and Dynamic datasets.
> Manage Dynamic Sets: FALSE Manage Jumbo Sets: FALSE
> syntax dbgenalt fileset(selection criteria), percent-full,
> dbgeneral-password
> e.g. %DBGENALT @(dbsetfullness>.7),.6,testa ((fuller than 70%, change
> cap to 60%))
>
> Not an IMAGE related file::: DBGCMD.DBGENALT.ATDBG(0)
> Not an IMAGE related file::: DBGCMDA.DBGENALT.ATDBG(0)
> Not an IMAGE related file::: DBGVE.DBGENALT.ATDBG(0)
> Not an IMAGE related file::: DBGVEE.DBGENALT.ATDBG(0)
> JUMBO flag off, not processed::: DBX01.DBGENALT.ATDBG
>Creator different than current logon::: DBX02.DBGENALT.ATDBG
(MANAGER:::MGR)
> Dynamic flag off, not processed::: DBX03.DBGENALT.ATDBG
> Processing Standard dataset::: DBX04.DBGENALT.ATDBG
> Processing Standard dataset::: DBX05.DBGENALT.ATDBG
> Processing Standard dataset::: DBX06.DBGENALT.ATDBG
>
>
>
> Not an IMAGE related file::: Indicates that currently
> processed file in the file set is not an IMAGE dataset. The file name is
> displayed along with the file code in parenthesis.
>
> JUMBO flag off, not processed::: Indicates that the
> currently processed file in the file set is a JUMBO dataset (Master or
> Detail) and the JUMBO management option is not enabled. To cause
> DBGENALT to manage JUMBO datasets, please 'SETVAR DBGENALT_JUMBO TRUE'.
>
> Creator different than current logon::: Indicates that the
> currently processed file in the file set has a creator different than the
> current logon. DBGENALT must be run from a logon that is the creator of
> the database. The file name is displayed along with the file creator and
> current logon user name (creator user name ::: logon user name).
>
> Dynamic flag off, not processed::: Indicates that the
> currently processed file in the file set is a Dynamic dataset (Master or
> Detail) and the Dynamic management option is not enabled. To cause
> DBGENALT to manage Dynamic datasets, please 'SETVAR DBGENALT_DYNAMIC
TRUE'.
>
> Processing Standard dataset::: Indicates that the currently
> processed file in the file set will be managed.
Tim Joseph, Technical Support
425-485-8536 (phone)
206-650-3101 (mobil)
[log in to unmask] (email)
425-485-7801 (fax)
http://www.bradmark.com/
|
