We have installed in customer the product RDT, we used only the volumes of his machine z/os (copied volumes environment).
For it, we copy RDT's IODF99 in his volumes, modify sys1.iplparm (loadxx) and the procedure consolxx of RDT.
The devicemap definition has more than 200 volumes and we have used the address '1Axx' ( 4 positions).
THE PROBLEMS:
1.By default the IODF has these devices addres ' OFFLINE YES ', Is posible change the parameter to 'offline no' into HCD in the current IODF?
2. we have created a duplicate to current IODF and having changed only the parameter to ' OFFLINE NOT ', but the system initialize with de old IODF( we have modify the loadxx).
Is possible that only can be copied with volumes of RDT product (ipl 0a80 parm 0a82dc + the volume to customer, for copy de IODF with the changes).
Thank you

You haven't given me much detail, however, it is certainly possible to create and/or modify the IODF shipped with the ADCD volumes supplied with RD&T.  You will need a driving system to do this.  I suggest you use the SARES1 volume shipped with the product which will allow you to build a basic one volume stand alone system after which you can bring up a TSO user and invoke the HCD dialogs.  Remember that RD&T supports at most, 1024 IO devices.  While we support 4 digit device definitions, the total number of active devices defined may not exceed 1024.  Also note that RD&T does not support logical channel subsystems.

RDzJohn

Thak you for your answers!

The point I was trying to make was you need a running system from which to run HCD.  You could use our stand alone system or one of your own. 

RDzJohn

RDT started with volumes to customer and this volum containt HCD product. The problem is when copy and modify the IODF,that don´t start using the new IODF  in ipl.
The rpegunta is :
1. How I can change the IODF started by the system ( the actual)?
2. The IODF to recognize it has to be created / copied / modified in RDT product ? 

You specify the IODF you want use for the ipl in the LOADxx member you use to ipl.  LOADxx can  be specified in SYS1.PARMLIB, SYS2.PARMLIB or SYS1.IPLPARM.  The system looks in SYS1.IPLPARM followed by the others.  On RD&T systems supplied by IBM, we use SYS1.IPLPARM.

You will find an IODF keyword followed by a number and a hlq.   On our systems the LOAD00 member contains

IODF   99  SYS1     this corresponds to SYS1.IODF99

RDzJohn

LOADXX has the parameters to the new IODF , but when ipl old IODF started.

The problem is when copy and modify the IODF, abount customer system, columes and HCD  (into RDT product),that don´t start using the new IODF in ipl. I

I think that the problem is because the IODF is created by volumes of the client and his HCD. Is it possible? The IODF that uses the system was created by RDT and his HCD?

1. How I can change porperties in the IODF actual?
2. To recognize it IODF has to be created / copied / modified using RDT product, with his volumes and ipl?

Were you able to resolve this issue? If so, could you append generally what you did to solve the problem?