On Thu, 21 Feb 2013 09:59:36 -0600, Jim Mooney <[email protected]> wrote:
>Thanks very much Art. It is easy enough to test the WTPMSG profile setting, so >I did. It appears to have no influence on this. I run my session with WTPMSG. >If I set my profile to NOWTPMSG, I still get the IGD msg for FileAid (while I >don't get it for ispf 3.2). Next, I edited the 'F2' clist provided by >Compuware, and changed it from 'CONTROL MSG' to 'CONTROL NOMSG'. When I >executed the clist I still get the msg. ...still a mystery to me, but, like I >said, we're going to change the volume count, so all this will be moot. The F2 Clist calls FADYNALOC which then calls FAEXEC, then others are invoked for specifc product functions. Any of these downstream CLISTs / EXECs could CONTROL MSG, overriding F2. >As a side note (I know I'm getting distracted here) some of the FileAid >clists, like 'F2', end with rc=12 when issued from ispf 3.4. It happens when I >exit the FileAid menu with PF3 to go back to DSLIST. FileAid works like a >charm, but when I PF3 back to ispf 3.4, the short msg says 'command failed'. >PF1 shows rc=12. Maybe you've seen that failure before? Maybe, but I don't recall. I don't see it here with v9.3.1. It sounds to like a case for our Support Center to investigate. Regards, Art Gutowski Compuware Corporation ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
