What in.0 in.1 etc. Holds?
בתאריך 23 בספט 2013 17:38, מאת "Lizette Koehler" <stars...@mindspring.com>:

> In case you were not aware, there is a newsgroup for TSO-REXX
>
> If you have not done so, you can join here.  Just go to the bottom of the
> Webpage
>
> http://www2.marist.edu/htbin/wlvindex?TSO-REXX
>
>
> what are the attributers?  Lrecl, blksize, etc...
>
> Did you check the original PDS to see if that member was readable?  Did it
> get an I/O Error?
>
>
>
> Lizette
>
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Rob Schramm
> Sent: Monday, September 23, 2013 7:32 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Rexx question
>
> All,
>
> I was doing some rexx work in batch on z/OS... attempting to use
>
>  "EXECIO * DISKR INPUTDD (Finis Stem in."
>  "FREE F(INPUTDD)"
>
> Where the INPUTDD was
>
> //INPUTDD DD DSN=SOME.PDS(MEMBER)
>
> and the results were very strange (multiple lines concatenated, seemed to
> be
> picking up a prior member in the PDS, corrupted data).  I ended up copying
> the PDS member to a sequential file and the problems went away.
>
> I have never had a problem reading a PDS member as a sequential file..
> until this occurred.  Is there some caveat to reading a PDS member as a
> sequential file?   Is the exception documented?
>
> I have been to the manuals, google, various articles on REXX, tutorials
> etc.. and not found anything to match (even loosely) what was happening.
>
>
> Rob Schramm
> Senior Systems Consultant
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to