ZOS test IODF configuration display/ create/ change-consoles/ compare using ISPF

CONTENTS:

 Bottom

 Case 1. Easy display parameters of the current I/O  configuration

Case 2. Easy create, change, delete    the parameters of the currently

created work I/O configuration

     2.1. Create (copy) new I/O definition file

     2.2. Change I/O Device  definition

     2.3. Delete I/O definition file if in error

Case3. How to build IODF  using ISPF/HCD

Case 4. How to prepare IPL with the new IODF  configuration

     4.1. Create LOAD library member

     4.2. IPL  from test LPAR BC3A with LOAD library member

Case 5. How to compare the new changed configuration data   with the old original

 

 

     These  5 examples of frequently  occurring cases  with test  IODF (Input Output Definition File)  configuration of LPAR  using HCD (Hardware Configuration Definition)  of TSO/ISPF are concerning the test  LPAR BC3A. The  descriptions  of the  cases bellow  explain how to: display  the old  work configuration IODF38,  create new IODF48 (by copy of old one), change device /consoles/  parameters and  delete (if IODF is wrong and require to create another) are followed by production IODF48  building,  IPL prepare (to copy the old LOAD2B and to create new member SYS1.IPLPARM(LOAD48) and  to compare  the old and the new configuration are they changed. The changes refer consoles addresses 0D00,16 excluded from the explicit device candidate list for LPAR BC2A, so that partition name description is omitted and during IPL these addresses are not dependent from LPAR name.

 

          Case 1. Easy display parameters of the current I/O configuration

(in  LPAR BC3A using HCD of TSO/ISPF)

Display1: TSO/ISPF – sd.log – display the name of the current disk configuration (to verify if it was  lost/forgotten)

(Use MVS  command  to see     the name of the current disk configuration –  SYS1.IODF38)

/D   IOS,CONFIG

IOS506I 12.27.59 I/O CONFIG DATA 661

ACTIVE IODF DATA SET = SYS1.IODF38

CONFIGURATION ID = BC1B           EDT ID = 35

Display2:  TSO – HC (HCD      – Hardware Configuration Definition)  –  display  the parameters of the current disk configuration if no IODF source is available

(Use TSO/ HC menu  to display  the parameters of the current disk configuration – I/O devices)

-HC

I/O definition file . . . ‘SYS1.IODF38’           (Enter)

11.  Define, modify, or  view configuration data    (choose 1)

2.  Activate or process configuration data

3.  Print or compare configuration data

4.  Create or view graphical configuration report

5.  Migrate configuration data

6.  Maintain I/O definition files

-5_ 1. Operating system configurations       (choose 5)

consoles

system-defined generics

EDTs

esoterics

user-modified generics

2. Switches

ports

switch configurations

port matrix

3. Processors

channel subsystems

partitions

channel paths

4. Control units

    5. I/O devices

–                           I/O Device List

Command ===>   loc 500_______________________      (locate 500 volume disk address)

–   Number Type +        CSS OS 1— 2-

/ 0500   3390          1   1  3A00 __                     (enter / to 0500)

–  Actions on selected devices

 8_ 1.  Add like  . . . . . . . . . . . . . (a)          (choose 8)

2.  Change  . . . . . . . . . . . . . . (c)

3.  CSS group change  . . . . . . . . . (g)

4.  OS group change . . . . . . . . . . (o)

5.  Device type group change  . . . . . (t)

6.  Prime serial number and VOLSER  . . (i)

7.  Delete  . . . . . . . . . . . . . . (d)

8.  View device definition  . . . . . . (v)       

–                            View Device Definition

Device number  . . . . . . . : 0500

Device type  . . . . .   .  . . : 3390

Device number  . : 0500     Device type  . : 3390

Preferred Device Candidate List

/ Proc.CSSID UA   Time-Out  STADET  CHPID     Explicit         Null

# BC1B       00   No        Yes               No               ___   Enter

 

– Device number  . : 0500     Device type  . . : 3390

Config. ID   Type     Description

 / BC1B         MVS                  (enter /to BC1B)

 

-Configuration ID . : BC1B

Device number  . . : 0500           Device type  . . . : 3390

Generic / VM device type  . . . . : 3390

ENTER to continue.

Parameter/

Feature    Value            R Description

OFFLINE    No                 Device considered online or offline at IPL   (currently is online)

DYNAMIC                       Device supports dynamic configuration

LOCANY                        UCB can reside in 31 bit storage

SHARED     No                 Device shared with other systems

SHAREDUP   No                 Shared when system physically partitioned

 

From this case it is clear that the disk volume with address 0500 will be in status online after  IPL.

The same display could be done for  Control units,  Processors, Switches, Operating system configurations.

 

          Case 2. Easy create, change, delete    the parameters of the currently created work I/O  configuration

Use sys1.iodf48.work   on  test LPAR using HCD of TSO/ISPF  as follows.

The sequence  is as follows:

– Copy new I/O definition file(create sys1.iodf48.work) using the currently the currently accessed IODF38  into another data set(2.1).

– Change I/O definition file description  (sys1.iodf48.work) (2.2)

– Delete I/O definition file –  if last sys1.iodf48.work is  in error (2.3)

               2.1. Create (copy) new I/O definition file

Use sys1.iodf48.work as follows.

-HC

I/O definition file . . . ‘SYS1.IODF38.work’   – (Enter)

6.  Maintain I/O definition files (I/O definition file . . . ‘SYS1.IODF38.WORK’ – the old  IODF to be used)   (choose 6)

– 2_       1.  Delete I/O definition file       (choose 2)

              2.  Copy I/O definition file               

3.  Change I/O definition file description

4.  View I/O definition file information

5.  Export I/O definition file

–            Source IODF name . . . ‘SYS1.IODF38.WORK’ –  old

Target IODF name . . .  ‘SYS1.IODF48.WORK’  – new (enter ‘SYS1.IODF48.WORK’ )

Activity logging . . . Yes   (Enter Y)

The specified target file does not exist.  To create a new

file, specify the following values.

Volume serial number . . BC2MCC                          (enter system volume BC2MCC)

Space allocation . . . . 720     (Number of 4K blocks)       (Enter 720)

Activity logging . . . . Yes    (Yes or No)                  (Enter Y)

 

Copy request confirmed  .  1  / Yes/   (Enter 1 for Yes)

IODF SYS1.IODF38.WORK copied to IODF SYS1.IODF48.WORK.

After copy – these files are created: p.3.4 – sys1.iodf48.work

SYS1.IODF48.WORK                                                          BC2MCC

SYS1.IODF48.WORK.ACTLOG          Browsed               BC2MCC

SYS1.IODF48.WORK.CLUSTER                                       *VSAM*

                2.2. Change I/O  Device definition

Use sys1.iodf48.work – (just created) as follows.

-HC

I/O definition file . . . ‘SYS1.IODF48.work’  (Enter)

– 1.  Define, modify, or  view  configuration data  (choose 1)

(I/O definition file . . . ‘SYS1.IODF48.WORK’ – the new IODF copied)

–   5__ 1. Operating system configurations           (choose 5)

5. I/O devices  

–  Command ===>   loc 0d00 (Console D00 to be independent from LPAR BC2A) (locate 0d00)

——-Device——- –#— ——–Control Unit Numbers + ——–

/ Number Type +        CSS OS 1— 2— 3— 4— 5— 6— 7— 8— Base

/ 0D00   3278-2        1   1  0D01 ____ ____ ____ ____ ____ ____ ____         (Enter / against 163A )

– 2_ 1.  Add like  . . . . . . . . . . . . . (a)     (choose 2)

2.  Change  . . . . . . . . . . . . . . (c)

– / Proc.CSSID  UA +  Time-Out  STADET  CHPID +    Explicit         Null

  / BC1B              00     No              Yes               __         Yes              No    (Enter / against BC1B)

STADET . . . . . . . . . . . . . Yes  (Yes or No)

Preferred CHPID  . . . . . . . . __  +

Explicit device candidate list . YES   (Yes or No)   – (for  all 0d00 – odof addresses  is still existing  and will be changed  to be  not  BC2A  dependent !)

–      Device number  . . . : 0D00      Number of devices  . . . : 1  -(for all  till 0d0f addresses is repeated)

Device type  . . . . : 3278-2

Processor ID . . . . : BC1B

Channel Subsystem ID :

/ Partition Name  Description               Reachable

_ BC1B                                              Yes

                 / BC2A                                              Yes        (will be omitted) (Enter / against BC2A)

_ BC3A                                              Yes

_ BC4A                                              Yes

Changes: 

– STADET . . . . . . . . . . . . . Yes  (Yes or No)      (enter Y)

Preferred CHPID  . . . . . . . . __  +

 Explicit device candidate list . No   (Yes or No)   – for all 0d00 – odof addresses  are not  (enter N)

BC2A  dependent !

Verify changes:

– 5. I/O devices

Command –         Loc 0d00         (locate console address 0d00)

——-Device——- –#—           ——– Control Unit Numbers + ——–

/ Number Type +              CSS OS 1— 2— 3— 4— 5— 6— 7— 8— Base

– / 0D00   3278-2              1      1     0D01 ____ ____ ____ ____ ____ ____ ____       (enter / to 0d00)

– 8__  1.  Add like  . . . . . . .   (enter 8)

8.  View device (console) definition

 

– Device number  . : 0D00     Device type  . : 3278-2

Preferred Device Candidate List

/ Proc.CSSID UA   Time-Out  STADET  CHPID     Explicit         Null

 # BC1B          00     No            Yes                             No               ___

(the result of verification: device 0D00  is excluded  (Explicit=No) from Device Candidate List – not fixed for BC2A partition)

                2.3. Delete I/O definition file if in error:

-HC

I/O definition file . . . ‘SYS1.IODF48.work’   (Enter)   

6.  Maintain I/O definition files (I/O definition file . . . ‘SYS1.IODF48.WORK’ – if last in error) (choose 6)

– 1_ 1.  Delete I/O definition file   (choose 1)

–  ‘SYS1.IODF48.WORK’ – confirm – Yes deleted

 

          Case3. How to build IODF using ISPF/HCD

If the new  ‘SYS1.IODF48. WORK’  is prepared in Case 2  do the following:

-HC

I/O definition file . . . ‘SYS1.IODF48. WORK ‘      (Enter)

-2   1.  Define, modify, or view configuration data       (choose 2)

       2.  Activate or process configuration data        

-1__  1.  Build production I/O definition file    (choose 1)

           2.  Build IOCDS

–                       Build Production I/O Definition File    Enter

Specify the following values, and choose how to continue.

Work IODF name . . . : ‘SYS1.IODF48.WORK’

Production IODF name . ‚SYS1.IODF48’__________________________

Volume serial number . BC2MCC  +

Continue using as current IODF:

2   1.  The work IODF in use at present

        2.  The new production IODF specified above        (choose 2)        

 -I/O definition file . . . ‘SYS1.IODF48’    – created

After build  – these files are additionally created: to view by p.3.4 – sys1.iodf48:

SYS1.IODF48               

SYS1.IODF48.ACTLOG        

SYS1.IODF48.CLUSTER       

SYS1.IODF48.WORK

SYS1.IODF48.WORK.ACTLOG

SYS1.IODF48.WORK.CLUSTER

 

          Case 4. How to prepare IPL with the new IODF configuration

               4.1. Create library LOAD member

Copy LOAD2B as LOAD48 changing to  IODF  from 2B  to   48 SYS1  for BC3A IPL:

IODF     48  SYS1     BC1B     08

NUCLEUS  1

NUCLST   00 Y

SYSCAT   BC2MCC113CCATALOG.MVSICFM.VBC2MCC

SYSPLEX  BC2APLEX

PARMLIB  SYS1.PARMLIB                                 *MCAT*

PARMLIB  CPAC.PARMLIB                                 *MCAT*

IEASYM   00

(Transfer and  save it on  PC-file: LOAD42_BC3A.docx)

                4.2. IPL  from test LPAR with library LOAD member

/sys1.iplparm(LOAD48) for BC2A test configuration at 7K  centre /

Verify the IPL volume addresses  for LPAR BCA/92 with MVS command in  TSO/ISPF sd.log with:

 

/D IPLINFO                                 

IEE254I  17.47.10 IPLINFO DISPLAY 164

SYSTEM IPLED AT 15.01.53 ON 04/07/2011

RELEASE z/OS 01.04.00    LICENSE = z/OS

 USED LOAD48 IN SYS1.IPLPARM ON 1904    

ARCHLVL = 2   MTLSHARE = N

IEASYM LIST = 00

IEASYS LIST = 00

IODF DEVICE 1904

IPL DEVICE 1900 VOLUME BC2RIC

Enter IPL  load menu  of HMC in CPU/Mainframe  and enter:

IPL device – 1900

IPL parm   – 190448

During IPL of  LPAR/BC3A (from old BC2A disk volumes) no problems exist with BC2A definitions eliminated by changes for 0d00,0d01 consoles, but  the real Master console  for LPAR/BC3A has  a different address 0c00 which conflicts with the  old BC2A disk volumes definitions. The solution  is  (after the first messages of  LPAR/BC3A on 0c00 console) to start and use  the HMC hardware console issuing the command: v cn(*),activate.

*** Remark: IOCDS could be created  following the rules in instructions for  IOCDS_creation  via HCD or HMC.

ZB_0903 – IOCDS created by IBM  and loaded manual with VSE LPAR.

ZB_1001– IOCDS created by IBM  and loaded manual without VSE LPAR.

 

          Case 5. How to compare the new changed configuration data   with the old original

-HC

I/O definition file . . . ‘SYS1.IODF48’    Enter

3_  1.  Define, modify, or  view configuration data   (enter 3)

2.  Activate or process configuration data

3.  Print or compare configuration data           

4.  Compare IODFs                         (enter 4)

New IODF name : ‘SYS1.IODF48’

Old IODF name . ‘SYS1.IODF38’______________________  +

–  Select compare reports             Limit ?

/_  Processor                       /  Yes                           (enter /  to Processor)

Switch                          /  Yes

Operating system                /  Yes

/  Device Attachment Compare    (enter /  to Device Attachment Compare)

/  Print inserted data   (enter /  to Print inserted data)

  /  Print deleted data    (enter /  to Print deleted data)

–  Print unchanged data

–  Print unchanged item IDs

IKJ56250I JOB FTPJES(JOB07452) SUBMITTED

//FTPJES   JOB (9999),MSGLEVEL=(1,1),MSGCLASS=X,TIME=1440,CLASS=B

//*

//COMP    EXEC PROC=CBDJCMPR,

// PARM.GO=// PARM.GO=(COMPARE,AB,CL,DA,,,,),

//             NEWIODF=’SYS1.IODF48′,

//             OLDIODF=’SYS1.IODF08′

New IODF name:  SYS1.IODF48    Old IODF name:  SYS1.IODF38

!——————————–!———————-!———————-!

! PROC  Device, Range     ! New IODF             ! Old IODF         !

!——————————–!———————-!———————-!

! BC1B  0D00,16               ! Actual Data          ! Old Data             !

!                                          !———————-!———————-!

!                                          !  >> old deleted      !  >> BC2A         !

!——————————-!———————-!———————–!

(BC2A parameter is deleted in sys1.iodf48 for IODEVICE ADDRESS 0d00-0dof attached to CU=0D01 for BC2A partition – look at kci88.zos140.base.lib(mvsio38) for the source of IODF38 to see the differences)

Incoming search terms:

  • iodf
  • iodf mainframe
  • mainframe iodf definition
  • mvs display iodf
  • zos command

Leave A Reply

Comments

No comments yet, be the first to add one!

Places

 

Clef two-factor authentication

woolrich outlet woolrich outlet online tiffany milano tiffany outlet tiffany outlet tiffany outlet tiffany outlet tiffany milano tiffany outlet peuterey outlet peuterey uomo hogan outlet hogan rebel hogan outlet hogan rebel hogan outlet hogan rebel hogan outlet hogan rebel hogan outlet hogan rebel hogan outlet hogan rebel roshe run pas cher roshe run parajumpers pas cher parajumpers soldes parajumpers pas cher parajumpers soldes parajumpers pas cher parajumpers soldes louboutin pas cher louboutin pas cher louboutin pas cher nike tn pas cher nike tn pas cher