What did the trick for me was:

1) Use the old script with

2) the new Version of DBGeneral

3) and the JCW below.

4) Added the SETJCW to MPEXMGR.PUB.VESOFT because the old
script launches sub-JOBs that don't know the JCW of the
parent job.  This is O.K. in my environment.

Reasons:

I needed to Globally alter the database sizes in the same account,
hence the need for "@.@".

Our databases all use the same Creator.  If the Creator was different,
then some user on our system illegally modified the database, the
obvious failure of a DBGENALT would flag me to that.)

Thanks.

Tracy Johnson
MSI Schaevitz Sensors


-----Original Message-----
From: Tim Joseph [mailto:[log in to unmask]]

Hello again,

I believe JCW (setjcw dbguserversion = 7217) is the 'fix' for the hang when
using DBGeneral 7.3 with the old command file, not the cause.  The JCW
alters the dialog of DBGeneral 7.3 to match the old DBGENALT.

I believe your choices are:

option 1:
--------

JCW: YES
DBGENALT: multi-account/group/user (old)
DBGENERAL: 7.3
JUMBO/Dynamic/B-Tree: NO

or

option 2:
--------

JCW: NO
DBGENALT: single account/group/creator (new)
DBGENERAL: 7.3
JUMBO/Dynamic/B-Tree: YES



tj

At 11:05 AM 12/19/00, Johnson, Tracy wrote:
>Ahhh, but the old JCW [snipped] is the one that hangs in 7.3,
>so I have a Catch22.  Either it hangs if I want to globally
>DBGENALT using the old script or I must hard-code the groups
>in the Account using the new script.
>
>(Note I composed the original message last week, not Terry
>Simpkins.  I was using his e-mail account while in China with him.)
>
>Tracy Johnson
>MSI Schaevitz Sensors




    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/