MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » January 2013

Re: What's wrong with this picture?



fixed

On 25 Jan 2013 09:11, DrFranken wrote:
IBM i 7.1 on POWER7 with TR5. This is a guest partition with
an IBM i host.

Work with Device Descriptions

2=Change 3=Copy 4=Delete 5=Display 6=Print 7=Rename
8=Work with status 9=Retrieve source

Device Type Text
TAP01 3580 CREATED BY AUTO-CONFIGURATION
TAP02 3580 CREATED BY AUTO-CONFIGURATION
TAP03 3580 CREATED BY AUTO-CONFIGURATION
TAP03 3580 CREATED BY AUTO-CONFIGURATION
TAP04 3580 CREATED BY AUTO-CONFIGURATION

This is only one object in QSYS with the name TAP03 however.

Presumably [it was left unstated] the command issued for which that display was presented, was the request to WRKDEVD DEVD(*TAP). Per the final observation "only one object", the effect of WRKDEVD DEVD(TAP0*) presumably would be a similar list, but without a duplicate name. If the device type 3580 reflects a tape library, the request to WRKDEVD DEVD(*MLB) or WRKDEVD DEVD(*TAPMLB) [and even WRKMLBSTS] might show similar information.

Any attempt to vary it on results in CPD8EB4 "Device vary on
failed."

Deleting one of them also deleted the other.

Curious.....

With a list menu using /names/ instead of pointers, the list actions would be performed against the name that can be resolved to a system pointer. So even if the two /names/ represented two distinct entities [e.g. from hardware resources assigned the same resource name], only one of those entities would be accessible from the menu; the one that can be resolved from the Machine Context by that object name.






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact