This message means a FILEDEF ddname CLEAR was issued where "ddname" was not "FILEDEFfed" before. Normally don't worry about it. At the other hand, the fact that this message appears on the console, often means that the executed REXX EXEC is running with the default ADDRESS CMS. No good design for code meant to run at various installations.
My guess is that the IODF was written correctly. You could open a PMR to have the EXECs used by HCD changed to run with ADDRESS COMMAND, making them more reliable. 2010/8/17 Barbara Andrews <bandr...@e1b.org> > I'm trying to use HCD in VM for the first time to write an IOCDS on at z10. > I have: > - Created a skeleton file > - Loaded the IOCP source into the skeleton file with CBDSMIGR > - Created a production IODF file > - Created a IOCDS input file by using: > CBDSIOCP IODF02 PRODIODF A ERIE2098 > - Now trying write to the IOCDS for the next POR (while logged on to user > CBDIODSP) by using: > CBDSIOCP IODF02 PRODIODF A ERIE2098 I A2 > (I have checked on the HMC for the z10 and A2 is not write protected.) > but getting error: > DMSFLD704I Invalid CLEAR request > The message indicates A CLEAR request was entered for a file definition > that does not exist > But I do not understand what I am supposed to do about a file definition. > Can anyone shed some light on this for me? Thanks. > > > > Barbara Andrews, Sr. Systems Software Specialist > Erie 1 BOCES / WNYRIC > (716) 821-7130 > * > > * > ------------------------------ > * > Confidentiality Notice: > This electronic message and any attachments may contain confidential or > privileged information, and is intended only for the individual or entity > identified above as the addressee. If you are not the addressee (or the > employee or agent responsible to deliver it to the addressee), or if this > message has been addressed to you in error, you are hereby notified that you > may not copy, forward, disclose or use any part of this message or any > attachments. Please notify the sender immediately by return e-mail or > telephone and delete this message from your system.* > -- Kris Buelens, IBM Belgium, VM customer support
