Not having access to TSO Pipes right now, I'll have to answer from experience.

I would check for proper DCB info (RECFM=nn,LRECL=nn and BLKSIZE= if not 
provided by an exit.).  EXECIO may have defaults that Pipes does not.

In batch, check for MSGLEVEL set for all messages to come out, and review the 
JES output.

Under TSO, check that MSG is on (I forget the exact syntax) and two or three 
other things that could supress messages and return codes.  

Seeing the messages won't solve the problem, but they might tell you (or us) 
where to look.

-----Original Message-----
From: CMSTSO Pipelines Discussion List [mailto:[email protected]] On 
Behalf Of Glenn Knickerbocker
Sent: Wednesday, April 13, 2011 1:08 PM
To: [email protected]
Subject: [CMS-PIPELINES] writing a temporary data set?

On TSO, I was given an exec that goes:

  'PIPE' etc. '| stack'
  'EXECIO * DISKW SYSIN ( FINI'

to write a temporary file to be used by another program.  If I try to
skip the stack:

  'PIPE' etc. '| > dd=sysin'

all I get is a complaint that it can't be opened.  What am I missing?

¬R

Reply via email to