|
View previous topic :: View next topic
|
| Author |
Message |
surya.kalyan
New User
Joined: 09 Jan 2007
Posts: 20
Location: Mumbai
|
|
|
|
| Code: |
/*REXX*/
INPUT = 'T.TCS.CR.KALYAN.TEMP'
X = OUTTRAP(MEMS.)
/* TO GET THE MEMBER LIST FROM THE INPUT PDS */
"LISTDS '"INPUT"' MEM"
X = OUTTRAP(OFF)
DO I=7 TO MEMS.0
MEMS.I = STRIP(MEMS.I)
SAY 'MEMBER:'MEMS.I
END
EXIT
|
In the above code mentioned which lists the members of a PDS, Can any one explain me why we use OUTTRAP for??
I did a QW but failed to understand the exact reason. |
|
| Back to top |
|
 |
PeD
Active User
Joined: 26 Nov 2005
Posts: 459
Location: Belgium
|
|
|
|
| To avoid receiving all superfluous messages from LISTDS and to be able to process the stem |
|
| Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
A few notes about OUTTRAP:
| Quote: |
In general, the OUTTRAP function traps all output from a TSO/E command. For example, OUTTRAP traps broadcast messages from LISTBC, the list of allocated data sets from LISTALC, catalog entries from LISTCAT, and so on.
If you plan to write your own command processors for use in REXX execs, and you plan to use the OUTTRAP external function to trap command output, note the OUTTRAP function does not trap command output that is sent to the terminal by:
TPUT
WTO macro
messages issued by TSO/E REXX (that is, messages beginning with IRX)
messages issued by TRACE output
However, OUTTRAP does trap output from the PUTLINE macro with DATA or INFOR keywords.
|
|
|
| Back to top |
|
|
Marso
REXX Moderator
Joined: 13 Mar 2006
Posts: 1353
Location: Israel
|
|
|
|
Just try without the OUTTRAP: the output of the LISTDS command will be displayed on your screen, and your REXX program will have no idea of what the result was.
OUTTRAP will just do what it says: it TRAPS the OUTput from TSO commands and make it available to the REXX program. |
|
| Back to top |
|
|
|
|
