IBM Mainframe Forum

Thanks Enrico, I'll give this a try.
The fact is, the EMC command I'm trying, gives the response after a small delay. I'm able to get the output using the @SYSCMD program example that's given in "Implementing REXX support in SDSF" guide but not able to with the working examples given above. I'm trying not to rely on pre-written functions.

I am so used to some <standard> coding that some <errors> never occur

using getmsg I <always> use the <timeout> argument ( 120 in my snippet )
so a slow response from the console command processor seldom bothers me

/soapbox on

I am very picky about jcl appearence,
good alignment, continuation at column 16 and friends

so a loong time ago performing an OS_390 installation
I got a worried call from the IBM support center for a sev 1 apar
( for a badly written jcl that would cause some install steps to fail )

when I said that I had not had any problems .... they wondered why
and somebody lost two days reserching why my client distribution tapes were good

after a while I realized that my pickiness had saved me
seeing a badly written jcl I had reformatted everything before running the whole jobstream
avoiding the jcl error

I was good enough to tell them

/soapbox off

120? Woah. I thought 60 was the limit! I'll try this and get back to you tomorrow.

One of the clients I work for does that too. It blows my mind each time I see his JCL or REXX or ASM, and I wonder - if he uses an IDE on his desktop for this. Editing in the mainframe is rather unpleasant.

EDIT: I'll be running this using IKJEFT01 in batch. Could that be the reason by any chance? I've tried with 60 and i still get no lines; though when I manually give the command, I get the lines well ahead of 60 seconds.