A symcfg disco is nondisruptive. You can do it anytime you need to get the latest info of the attached Symms. In fact, it's even a good idea to refresh is before starting a series of symcli commands (unless you know for a fact nothing much has changed).
As RRR said first thing I do is a symcfg discover or I restrict it with a -sid xxxx and you can also do a symcfg -sid xxxx verify to bounce the database against the machine to check that its up to date.
lengthy is a good word for it. I have a hard time getting the guys to run it before doing config work since we have ~16k devices on the local symm and another ~20k on a remote symm with an SRDF/A link
Well, when you have mainframe mixed in with the Open Systems, and the mainframe guys still insist on using MOD-3 devices for most of their capacity... it adds up to a lot of devices. On our Prod array they account for about 20% of our capacity and about 80% of the devices (by count).
RRR
4 Operator
•
5.7K Posts
0
August 6th, 2009 03:00
RobertDudley
2 Intern
•
448 Posts
0
August 6th, 2009 04:00
Mosa3lyan
265 Posts
0
August 6th, 2009 07:00
RRR
4 Operator
•
5.7K Posts
0
August 7th, 2009 00:00
Allen Ward
4 Operator
•
2.1K Posts
0
August 11th, 2009 08:00
Sometimes I'm tempted to skip it myself!
RRR
4 Operator
•
5.7K Posts
0
August 12th, 2009 03:00
Allen Ward
4 Operator
•
2.1K Posts
0
August 17th, 2009 13:00