Larry, I tried using dbadgalt in a Streamx job, using commands similar
to what you use, although I like your approach more :-). But what I
don't like about dbadgalt is the fact that it streams another  job
(zzstream.cmd22.vesoft), and I want to keep everything within one job.

Larry Barnes wrote:

>  If you have Vesofts, MPEX you could do something like this:
>
>  listf [log in to unmask](dbsetfullness>.78),db
>  if mpexnumsucceeded > 0
>   copy [log in to unmask],[log in to unmask];yes
>   listf [log in to unmask],db
>   dbadgalt [log in to unmask](dbsetfullness>.78), 0.6
>   echo
>   echo ========= AFTER ==========
>   listf [log in to unmask],db
>   echo -------------------------------------------
>  endif
>
> You supply how full you want to check for, in the example it is .78 or
> 78% full.  If a data set is more than 78% full MPEX first makes a
> backup copy of the data base and then runs the Adager command
> 'dbadgalt'.  This will run Adager and change the capacities of all
> data sets that match the selection criteria.  In the example this
> would be any db file that starts with 'prdb'.
>
> Hope this helps.
>
> Jay Willis wrote:
>
>> Hi all,
>>
>> We are using Adager version 000304. I want to be able to stream a
>> job to change the capacity of any of the datasets in an Image
>> database.
>> I want the job to prompt for the dataset that I want to change, and
>> the
>> percentage capacity that I want to change the dataset to.
>>
>> I would like to perform the change in batch rather than in a command
>>
>> file, so that the stdlists can be archived. When I streamed such a
>> job
>> the stdlist said that, in batch, Adager ignores MPE commands.
>>
>> Jobs could be created for each individual dataset, but I would like
>> to
>> have just one generic job to handle any dataset whose capacity is
>> becoming too large.
>>
>> Any help would be appreciated.
>> Jay
>
> --
> Larry Barnes
> Director of I.T.
> Mitek Corp.
> 602-438-4545 x1366
> Phoenix, AZ 85040
>
> Check Us Out !
> http://www.mitekcorp.com
>