Hi Raymond,
I believe the reason you're not getting any TRF files in this scenario is
that the SET EDEVICE command is very analogous to the SET RDEVICE command.
You can define whatever you would like for either command, but VM will
not attempt to do anything with the device created from either one until
you issue a VARY ON.
Having said that, I'm not certain a TRSOURCE of your FCP device will be
terribly helpful for the problem you're having. You're welcome to try, of
course, but let me offer an alternative.
If you're concerned about being able to use LUN 0000, and not LUN 0001, I
would suggest the SCSIDISC EXEC that is shipped with z/VM as a sample
program. SCSIDISC EXEC and it's cousin RXSCSIFN MODULE (must be renamed
RXUSERFN if 5.3 or earlier) will let you take an FCP subchannel that is
attached to your guest, and learn about the SAN elements visible from it's
point of view. Often times one can discern the problem by knowing what
each subchannel can actually see, as the problems with EDEVICE or YAST
will become more obvious. For example, the actual LUN numbers that are
visible, or WWPNs that are accessible via the SAN ACLs.
Regards,
Eric
Eric Farman
z/VM I/O Development
IBM Endicott, NY
The IBM z/VM Operating System <[email protected]> wrote on
02/10/2009 03:06:19 PM:
> From:
>
> Raymond Noal <[email protected]>
>
> To:
>
> [email protected]
>
> Date:
>
> 02/10/2009 03:34 PM
>
> Subject:
>
> Tracing FCP devices.
>
> Dear List:
> I am trying to trace the creation of an EDEVICE by using TRSOURCE
commands. It
> appears that there is no ‘traditional’ I/O done during this process.
> I used the following TRSOURCE commands:
> /* rexx */
> /* */
> 'CP TRSOURCE DROP SET FCP'
> /* */
> 'CP TRSOURCE ID LUN0 SET FCP TYPE IO DEV C600 USER MAINT IODATA 128'
> /* */
> 'CP TRSOURCE ENABLE SET FCP'
> /* */
> I then issued the SET EDEVICE as follows:
> SET EDEVICE 200 TYPE FBA ATTR SCSI FCP_DEV C600 WWPN
> 50060E8003275403 LUN 0000000000000000
> EDEVICE 200 was created and associated with FCP device C600.
> I then issued the CP commands:
> CP TRSOURCE DIABLE ALL
> CP TRSOURCE DROP ALL
> There was no TRFile created.
> This is starting to look like one has to do a ‘cptrace’ to capture
> any diagnostic data.
> The reason for my interest in this is because I can create an FCP
> device in my SuSE SLES 10 SP 2 virtual machine by attaching real
> (FCP) device C600 and I can use YAST è zFCP è Add to create a device
> using LUN zero, but I am not able to create (Add) a device using LUN
0001.
> Any assistance greatly appreciated.
> TIA
> HITACHI
> DATA SYSTEMS
> Raymond E. Noal
> Senior Technical Engineer
> Office: (408) 970 - 7978
