Device naming
ga
displays/printers anything I want? I am thinking if I configure
devices I can name them whatever I want, like JOHN, DAVID, HARLEY,
FRED, and Printers could be SAM, SALLY, RICK, ERIC, and that will
work??
But if I plug in a new device or start a new iseries access session it
will automatically name it "DSPxxxxxxx" or "PRTxxxxxxx".
Is that correct or are there any other issues I need to be
cognizant/aware of? Not that I would name the sessions with peoples'
names, just using them for illustration...that I can name a Display
JDHDSP001 for instance or a printer JDHPRT001...
thanks,
ga
iseriesflorida
You have 3 values for this system value (*NORMAL, *S36, *DEVADR) I
did help on these and they are pretty much as you describe. With the
system value QAUTOCFG turned on any device that the system recoginizes
as new it will create it accordingly, you can then rename it. If you
shut off QAUTOCFG I believe you can create your devices using the
manual method and then avoid what the QDEVNAMING system value is going
to create. You might get some other folks to reply to this and state
otherwise. I would probably let the system auto create what you need
then rename it accordingly.
ga
CRPence
> On Nov 3, 9:25 am, ga wrote:
>> If my system value QDEVNAMING is set for *normal, can I name
>> displays/printers anything I want? I am thinking if I
>> configure devices I can name them whatever I want, like JOHN,
>> DAVID, HARLEY, FRED, and Printers could be SAM, SALLY, RICK,
>> ERIC, and that will work??
Yes.
>> But if I plug in a new device or start a new iseries access
>> session it will automatically name it "DSPxxxxxxx" or
>> "PRTxxxxxxx".
Yes, if the appropriate auto-configure features are enabled.
>> Is that correct or are there any other issues I need to be
>> cognizant/aware of? Not that I would name the sessions with
>> peoples' names, just using them for illustration...that I can
>> name a Display JDHDSP001 for instance or a printer JDHPRT001...
>>
>
> You have 3 values for this system value (*NORMAL, *S36, *DEVADR)
> I did help on these and they are pretty much as you describe.
> With the system value QAUTOCFG turned on any device that the
> system recognizes as new it will create it accordingly, you can
> then rename it. If you shut off QAUTOCFG I believe you can
> create your devices using the manual method and then avoid what
> the QDEVNAMING system value is going to create. You might get
> some other folks to reply to this and state otherwise. I would
> probably let the system auto create what you need then rename it
> accordingly.
In my experience the setting of QAUTOCFG does not matter much for
cases of creating "devices using the manual method" because then a
request either uses named device support to target a named device,
or the existence of the local devices /manually configured/ will
preclude any need for an auto creation. The problem is only for
when a mis-typed name might result in creating a new device. Since
QAUTOCFG is not for virtual devices, and over time fewer & fewer
devices are physically attached [i.e. local], that specific auto
configuration feature is not very relevant in many shops. Yet for
any local devices I would also use the auto-configuration to effect
[*DEVADR named devices is my preference] and then rename as desired,
just as noted above.
Regards, Chuck
Dr.Ugo Gagliardelli
> If my system value QDEVNAMING is set for *normal, can I name
> displays/printers anything I want? I am thinking if I configure
> devices I can name them whatever I want, like JOHN, DAVID, HARLEY,
> FRED, and Printers could be SAM, SALLY, RICK, ERIC, and that will
> work??
QDEVNAMING sysval cannot help you tha way you want. If devices are tight
to clientAccess emulator sessions you can configure ca sessions to name
the device based on the neme of the pc or the name of the current user.
But each session must have a unique name, you can have ca creating
unique names flagging the check box. This way ca will create devices
depending on how many session were created, e.g if John created 3
sessions ca will create 3 devices JOHN1, JOHN2 and JOHN3.
> But if I plug in a new device or start a new iseries access session it
> will automatically name it "DSPxxxxxxx" or "PRTxxxxxxx".
>
> Is that correct or are there any other issues I need to be
> cognizant/aware of? Not that I would name the sessions with peoples'
> names, just using them for illustration...that I can name a Display
> JDHDSP001 for instance or a printer JDHPRT001...
If devices are local devices, attached via twinax, you can rename
autoconfigured devices and each time the device power on it will be
connected to the renamed device. If they are not local, so they parhaps
are virtual, renaming them will not help, possibly it will confuse you
instead, e.g. if a ca session does not configure any device name, the
auto config routine will assign the first available virtual device.
--
Dr.Ugo Gagliardelli,Modena,ItalyCertifiedUindoscrasherA�ejoAlcoolInside
Spaccamaroni andate a cagare/Spammers not welcome/Spammers v�o � merda
Spamers iros a la mierda/Spamers allez vous faire foutre/Spammers loop
schijten/Spammers macht Euch vom Acker/Spamerzy wypierdalac'
trans am kid
scenerio. Of course not using CA (all that much) but even them I go in
and name. You don't say if these are physically attached (i.e. twinax)
or if they are ethernet.
All 150+ devices on my new i are named the way I want them, not some
dippy system derived name. So it can be done. And I am set up for
autoconfigure and it all works fine.
chris