Re: PCHID WWPN report [EXTERNAL]

2022-03-02 Thread Mainframe Sysprog
Thanks Paul. It did list me the WWNN and WWPN but I believe those are for
the DASD subsystem that the paths connect to.

What I am looking for is a similar process to obtain the WWPN of the PCHIDS
on the processor end. This was still something new for me. Thanks for
sharing that.

On Wed, Mar 2, 2022 at 9:18 PM Feller, Paul <
02fc94e14c43-dmarc-requ...@listserv.ua.edu> wrote:

> You might consider trying ICKDSF with the ANALYZE option.  I used it to
> create a cross reference of PCHID to DASD port for the EMC DASD boxes we
> have.
>
> Sample of what I used.
> //ZOS1D3E  EXEC PGM=ICKDSF,REGION=128M
> //SYSPRINT DD SYSOUT=*
> //DSFDUMP  DD SYSOUT=*
> //SYSINDD *
>   ANALYZE UNIT(1D3E) NODRIVE NOSCAN HOSTACCESS(ALL)
> /*
>
>
> Paul Feller
> GTS Mainframe Technical Support
>
> -Original Message-
> From: IBM Mainframe Discussion List  On Behalf
> Of Mainframe Sysprog
> Sent: Wednesday, March 2, 2022 9:21 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: PCHID WWPN report [EXTERNAL]
>
> GM Listers,
>
> I want to obtain the WWPN of all PCHIDS on a processor and want to know
> what would be the fastest/easiest way to do that.
>
> The objective here is to do kind of an audit of what's connected to where
> for a new configuration and cross check it with intended HW configuration.
> I have the report from the switch which shows the WWPN to which is
> connected to, so if I can somehow get a report from the CEC listing the
> PCHID and its WWPN, I can cross check what's cabled up and what's not.
>
> Right now the way I do this is go into individual PCHIDS and do a problem
> determination from the HMC.
>
> Any help or pointers would be much appreciated.
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email
> to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> --
> Please note:  This message originated outside your organization. Please
> use caution when opening links or attachments.
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: PCHID WWPN report [EXTERNAL]

2022-03-02 Thread Feller, Paul
You might consider trying ICKDSF with the ANALYZE option.  I used it to create 
a cross reference of PCHID to DASD port for the EMC DASD boxes we have.

Sample of what I used.
//ZOS1D3E  EXEC PGM=ICKDSF,REGION=128M  
//SYSPRINT DD SYSOUT=*  
//DSFDUMP  DD SYSOUT=*  
//SYSINDD * 
  ANALYZE UNIT(1D3E) NODRIVE NOSCAN HOSTACCESS(ALL) 
/*  


Paul Feller
GTS Mainframe Technical Support

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Mainframe Sysprog
Sent: Wednesday, March 2, 2022 9:21 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: PCHID WWPN report [EXTERNAL]

GM Listers,

I want to obtain the WWPN of all PCHIDS on a processor and want to know what 
would be the fastest/easiest way to do that.

The objective here is to do kind of an audit of what's connected to where for a 
new configuration and cross check it with intended HW configuration.
I have the report from the switch which shows the WWPN to which is connected 
to, so if I can somehow get a report from the CEC listing the PCHID and its 
WWPN, I can cross check what's cabled up and what's not.

Right now the way I do this is go into individual PCHIDS and do a problem 
determination from the HMC.

Any help or pointers would be much appreciated.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
Please note:  This message originated outside your organization. Please use 
caution when opening links or attachments.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN