Very Computer

the article, 20 in technotes on picksys's web site ,about
resizing the vme works except for 1 small detail, the
article doesnt tell you to save the mds entrys for all your
fsi accounts first.

what is left out is to
1 create-file save.mds 1 1
in some fsi account
2 get-list vme-1 (list of all fsi accounts)
3 copy mds
(save.mds

after the steps in article 20 are all completed,
copy save.mds * (o
(mds

completes the job

Greetings,

That's strange.  I just did that technique today.

I did not save anything from the MDS this time, nor any time in the past
that I have done the same thing.

All of the QS pointers were miraculously recreated when I rebooted the
system and started up D3.

Now - I don't have any passwords or anything special in the MDS entries, so
I see no reason to save them.

Somebody else might need to save them.

Larry Hazel

Quote:> the article, 20 in technotes on picksys's web site ,about
> resizing the vme works except for 1 small detail, the
> article doesnt tell you to save the mds entrys for all your
> fsi accounts first.

> what is left out is to
> 1 create-file save.mds 1 1
> in some fsi account
> 2 get-list vme-1 (list of all fsi accounts)
> 3 copy mds
> (save.mds

> after the steps in article 20 are all completed,
> copy save.mds * (o
> (mds

> completes the job

If your mds items are generic, then there should be no need for the steps
you mention.
Part of the system coldstart is to do qs.upd.  This builds your qs items in
the mds file and through doing this, all of your fsi accounts will be
available.   You can test this by removing the mds item for one of your fsi
accounts.  Then, at TCL, type in qs.upd.  This will set up your mds item you
just removed.
Note - qs.upd will build new mds items for fsi accounts.  It also will
remove mds items if the fsi account no longer exists.
--
Simon Peters

Quote:> the article, 20 in technotes on picksys's web site ,about
> resizing the vme works except for 1 small detail, the
> article doesnt tell you to save the mds entrys for all your
> fsi accounts first.

> what is left out is to
> 1 create-file save.mds 1 1
> in some fsi account
> 2 get-list vme-1 (list of all fsi accounts)
> 3 copy mds
> (save.mds

> after the steps in article 20 are all completed,
> copy save.mds * (o
> (mds

> completes the job

I agree with Larry. I had someone try and tell me that needed to be done too
the first time I tried it, but the operation did it, as I like to say
"automagicly".

Hans Fehlow

Quote:> the article, 20 in technotes on picksys's web site ,about
> resizing the vme works except for 1 small detail, the
> article doesnt tell you to save the mds entrys for all your
> fsi accounts first.

> what is left out is to
> 1 create-file save.mds 1 1
> in some fsi account
> 2 get-list vme-1 (list of all fsi accounts)
> 3 copy mds
> (save.mds

> after the steps in article 20 are all completed,
> copy save.mds * (o
> (mds

> completes the job

if the mds items are generic, there's no need to save them
first. example:
ACCOUNT 001
001 QS
002 FSI:001A
this MDS entry is not automatically rebuilt because the
fsi account name is different from the MDS item name