Why does EXECIO require 'Enter' more than once?

Time Sharing Option, Interactive System Productivity Facility and REstructured eXtended eXecutor

Moderator: mickeydusaor

Post Reply
Javed Husain
New Member
Posts: 2
Joined: Sat Nov 08, 2014 1:53 pm

Why does EXECIO require 'Enter' more than once?

Post by Javed Husain »

Hi,

I have observed that when I am using "EXECIO * DISKW DDNAME", REXX will continue pulling input from the stack and from terminal input until it gets a null line. So a users will have to hit enter once to generate a null line. Why does EXECIO require 'Enter' more than once? Can there be better way of doing it? As of now I use the following two methods to overcome this:
  1. Used the Queued() built in function instead of '*'.
  2. Queued a null line before writing data from the stack.
nicc
Global Moderator
Global Moderator
Posts: 691
Joined: Wed Apr 23, 2014 8:45 pm

Re: Why does EXECIO require 'Enter' more than once?

Post by nicc »

It needs an EOF. But why use EXECIO, which is more designed for dataset access, when you can use PULL?
Regards
Nic
Post Reply

Create an account or sign in to join the discussion

You need to be a member in order to post a reply

Create an account

Not a member? register to join our community
Members can start their own topics & subscribe to topics
It’s free and only takes a minute

Register

Sign in

Return to “TSO, ISPF & REXX (Do you still do CLIST?!).”