The requirement for ULOG display is similar to the requirement for GETMSG: the system has to recognize output as a response to a user's command. I repeat what I said earlier: MODIFY task-name... has been problematic for me in the past. I know nothing of the internals, but MODIFY responses are essentially asynchronous WTOs from the named task. They are not 'MVS messages'.
If you run SMCS consoles, the SMCS console name must be distinct from the ULOG console name. If more than one instance of a given name is found, the 'first one' will get all messages directed to that name. That being said, your results should be consistent for all commands. Either ULOG gets all responses, or ULOG gets none of them. If you get inconsistent behavior, I suggest opening an SR with IBM for an *IBM* supplied task. Leave ADABAS out of the conversation for now. I was blown away to read that D A,L does not come back to ULOG. That is weird beyond belief. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jorge Garcia Sent: Wednesday, September 20, 2017 7:55 AM To: [email protected] Subject: (External):Re: GETMSG null with out ADABAS command Hi Elardus, I think this is not the problem. We can enter any comand in the system in ULOG, but some don't show the output command in the SDSF. Only in LOG (SYSLOG) ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
