You could open a case to BMC and request further help. I usually find the vendor support areas most helpful.
If you could post the command issued by Control-O to show us the extra information, we might be able to make suggestions. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of ??? ?? ??? > Sent: Tuesday, October 22, 2013 11:22 PM > To: [email protected] > Subject: Re: Command output not displayed on Console > > I'm not very proficient in Control-O. > Does anyone have a suggestion on how to fix this? > All the Control-O rule does is add some extra parameters to the $DI command. > > Gadi > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of [email protected] > Sent: Wednesday, October 23, 2013 9:12 AM > To: [email protected] > Subject: Re: Command output not displayed on Console > > > The command output shows INTERNAL. Are you issuing the command from the > internal reader or thru some strange product? Is there an automation product that is > suppressing the original command and re-issuing it with the options? > > The command was issued from STC09092, which he said is control-O. My guess is > that the command was issued using some CONTROL-O interface (that I don't > know), which in turn is using MGCRE *without* an explicitly defined EMCS console > and instead using console id 0 which translates to INTERNAL. And Control-O > apparently doesn't get the responses to a command and displays them properly. > > The question is if the operators can see the command response when they use a > true console and issue the command directly. > > Barbara > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
