On Tuesday, 08/17/2010 at 02:11 EDT, Kris Buelens <[email protected]> wrote: > 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.
Kris, I think you are making too many assumptions. That code path may believe that a ddname should have been defined, but wasn't. What went wrong? Were files written to the expected/documented place? I think the PMR is in order since, either way, there is something wrong in CBDSIOCP. Messages that should not appear should, like, you know, not appear. IMO, a PMR response of "you can safely ignore the message" should not be accepted. If a program has something useful (meaningful) to say, it should say it. Otherwise it should keep its mouth closed. "En boca cerrada no entran moscas." (I find it archaeologically interesting that DMS704I is actually an informational message when the text of the messages uses the word 'invalid'. Something that is not valid is an error, not just informative. Go figure.) Alan Altmark z/VM Development IBM Endicott
